Network based business to business portal for the retail convenience marketplace

ABSTRACT

Broadly, the invention provides an Electronic Marketplace Solution (EMS) which may be embodied, in part or in whole, as a method, system or computer readable medium of instructions. The invention provides a business to business Internet portal serving companies operating within the convenience marketplace. In one embodiment, the invention is an Internet portal which assists: Independent Convenience Retailers through the provision of a single system to sell, buy and pay for goods/services and manage their business more effectively; Organised Convenience Groups, by providing them access to improved network management, the ability to ensure compliance and the ability to reduce costs; FMCG Manufacturers in the areas of secondary supply chain efficiencies, by improved business intelligence and direct access to Convenience Retailers; Wholesalers/Logistics Providers, for reduced costs and improved efficiency and enabling them to expand their customer base; and/or Service Providers, by enabling them to more efficiently reach a large target market.

TECHNICAL FIELD

[0001] The present invention relates to a new type of network based business to business portal, and in particular, to a method of, system for, or computer readable medium of instructions for, providing a new type of Internet based business to business portal for the retail convenience marketplace.

BACKGROUND ART

[0002] Presently, the Australian retail convenience store market is estimated to generate annual revenues of AUD$10bn—AUD$12bn and consist of up to 60,000 outlets of which 75% are classified independent stores and 25% organised stores. The supply chain to this large number of retail outlets is costly and largely inefficient due to a high level of independent ownership and market fragmentation. This problem exists in many other retail convenience store marketplaces throughout the world.

[0003] The four key participants/groups involved in the convenience marketplace include:

[0004] Convenience Retailers—includes Organised Convenience, Independent Convenience/Route, Specialty Stores and Independent Supermarkets and Grocers;

[0005] Fast Moving Consumer Goods (FMCG) Manufacturers—includes Suppliers whose products are purchased by Convenience Retailers;

[0006] Wholesalers/Logistics Providers—includes any businesses providing product distribution services to Convenience Retailers and for FMCG Manufacturers;

[0007] Service Providers—includes any businesses providing “not for on-sale” products and services to Retailers, FMCG Manufacturers and/or their staff.

[0008] This supply chain and process complexity identifies a need to provide Retailers and Manufacturers, inter alia, a means to increase overall supply chain effectiveness.

[0009] There is a need to address the key business issues faced by the Convenience Retailer and to offer a solution which provides real value. A solution should have the ability to address the needs of key participants in the retail convenience store supply chain. These participants include Convenience Retailers, FMCG Manufacturers, Wholesalers/Logistics Providers and Service Providers.

[0010] Convenience Retailers:

[0011] The Retailer channels are generally those where consumer purchases are largely impulse or for immediate consumption. These channels include, but are not exclusive to, Organised Convenience, Independent Convenience/Route, Newsagents, Independent Grocery and Specialty Stores. There exists a need to provide such Retailers with a convenient means of accessing, ordering, handling payments, recording, managing and/or the like, goods, supplier details and/or other aspects of a Retailer's trade.

[0012] FMCG Manufacturers:

[0013] As an illustrative example, AC Nielsen estimates that at least 65% of the Australian convenience store market is supplied by fewer than ten manufacturers. Sales by individual manufacturers to these convenience stores can range from 5% of total deliveries (generally dry grocery products) to 50% (commonly impulse brand products such as chocolate bars, tobacco products and soft drinks). There exists a need to provide FMCG Manufacturers with a convenient means of supplying, offering for supply, ordering, arranging delivery, recording, managing, handling payments, and/or the like, goods, customer's details and/or other aspects of a Manufacturer's trade.

[0014] Wholesalers/Logistics Providers:

[0015] In Australia, approximately 25% of products sold in convenience stores are sourced through Wholesalers. The current wholesale market is characterised by various organised groups with differing operating arms and formats and a lack of a single nationwide organisation. There exists a need to provide a single portal for the various Wholesalers to reach the targeted Retailers.

[0016] Logistics Providers include businesses providing deliveries (and associated services) to the targeted Retailers. Industry consolidation in the Australian market, for example, has, at present, left only a few major players. There exists a need to provide a single portal for Logistics Provider's to reach/service the targeted Retailers, Wholesalers and/or Manufacturers.

[0017] There exists a need to provide Wholesalers and/or Logistics Providers with a convenient means of supplying, offering for supply, ordering, arranging delivery, recording, managing, handling payments, tracking and optimising logistics, and/or the like, goods, customer's details, supplier's details and/or other aspects of a Wholesaler's and/or Logistics Provider's trade.

[0018] Service Providers:

[0019] There are a number of organisations providing products and services (not for on-sale) to Retailers, FMCG Manufacturers, and/or their staff. These include providers of banking and insurance services, building and maintenance products, telecommunications services and lifestyle products. There exists a need to allow these providers to offer additional services to Retailers, Wholesalers, Logistics Providers and/or Manufacturers through a business exchange mechanism in an efficient manner.

[0020] Within the Retail Industry, it is presently known to individually provide:

[0021] Point of Sale (POS) scanning, that is sales information capture; or

[0022] Calculation of a replenishment order based on sales; or

[0023] Electronic transfer of store order to a web ordering site; or

[0024] Integration of a store order to web-based browse and buy functionality.

[0025] However, the combination of these features to provide an electronic marketplace solution, which in a non-limiting form may be embodied, at least partly, as a software marketplace solution, is not presently known and represents a problem to be overcome for the benefit of the convenience retail industry.

[0026] Presently, the following systems, individually, are available as stand-alone systems within the retail industry:

[0027] Available To Promise (ATP) checking from supplier's inventory database; or

[0028] Electronic transfer of checked order to supplier's order capture system; or

[0029] Supplier confirmation of order acceptance and fulfilment.

[0030] However, the combination of these systems to provide an electronic marketplace solution, which in a non-limiting form may be embodied, at least partly, as a software marketplace solution, is not presently known and represents a problem to be overcome for the benefit of the marketplace. This identifies a need to provide an end to end process for the order capture and order fulfilment within an e-commerce electronic marketplace solution for the convenience retail industry.

[0031] Furthermore, the integration of electronic payment processing with a combination of the aforementioned services/systems is, to the Applicant's knowledge, not presently known. There exists a need for a new integrated system of electronic payment processing provided with a combination of the aforementioned functions.

[0032] Presently, the provision of valued information regarding goods purchases by consumers to all or part of the convenience retail industry, that is, for example, manufacturers, store owners, wholesalers and logistics providers, is significantly limited. There exists a need to provide an improved means to obtain, access, manage and/or distribute this information.

[0033] Definitions:

[0034] The term “supplier” should be taken as a reference to the manufacturer, distributor or wholesaler selling the products to the retailer.

[0035] In a networked data communications system, users have access to terminals which are capable of requesting and receiving information from local or remote information sources. In such a system a terminal may be any type of computer or computerised device, a personal computer (PC), a mobile or cellular phone, a mobile data terminal, a portable computer, a personal digital assistant (PDA), a pager, a thin client, or any other similar type of electronic device. The capability of the terminal to request and/or receive information can be provided by an application program, hardware or other such entity. A terminal may be provided with associated devices, for example an information storage device such as a hard disk drive.

[0036] In such a system an information source may be a server or any other type of terminal (for example, a PC computer) coupled to an information storage device (for example, a hard disk drive). The exchange of information (i.e., the request and/or receipt of information) between the terminal and the information source, or other terminal(s), is facilitated by a connection referred to as a communication channel. The communication channel can be physically realised via a metallic cable (for example, a telephone line), semi-conducting cable, an electromagnetic signal (for example, a radio frequency (RF) signal), an optical fibre cable, a microwave link, a satellite link or any other such medium or combination thereof connected to a network infrastructure.

[0037] The infrastructure may be a telephone switch, a base station, a bridge, a router, or any other such specialised component, which facilitates the connection between the terminal and the network. Collectively, the interconnected group of terminals, physical connections, infrastructure and information sources is referred to as a computer network or data communications network.

[0038] The computer network itself may take a variety of forms. It may be located within a local geographic area, such as an office building, and consist of only a limited number of terminals and information sources. This type of computer network is commonly referred to as a Local Area Network (LAN). On a broader scale, it may be larger and support more users over a wider geographic area, such as across a city. This type of network is commonly referred to as a Wide Area Network (WAN). On an even broader scale LAN and WAN networks may be interconnected across a country or globally. An example of a globally connected computer network is the Internet.

[0039] To a user the Internet appears to be a single unified computer network, although in reality it consists of many different types of computer platforms utilising many diverse data communications technologies. The technologies are connected together in such a manner so they appear transparent to the user. This transparency is made possible through the use of a standard communications protocol suite known as Transmission Control Protocol/Internet Protocol (TCP/IP).

[0040] The Hyper-text Mark-up Language (HTML) and Hyper-text Transfer Protocol (HTTP) have developed to make the Internet or World Wide Web very accessible. The exchange of information on the Internet is further facilitated through hyper-text documents. Hyper-text documents are unique in that they use tags to define links which, when selected, fetch the related information from within the same document or from a new document altogether. The links are defined using HTML which provides a document formatting method which adapts in a consistent manner to any computer on which it is displayed. HTML tags are used to define the various components of an ASCII text file, image or sound which make up a hyper-text document, including such things as formatting and linking to other documents. HTML tags which link documents on one Internet information source to those on another do so by associating a Uniform Resource Locator (URL) with the referenced information. The ability to link Internet files of similar and/or differing formats to each other, and to link documents on other Internet sites, is a powerful feature of the Internet.

[0041] The appeal of the Internet is the large-scale interconnection of public and private networks. A concern exists, however, about “unauthorised” access from public networks to the attached private networks. This concern has resulted in the development of proxies. A proxy is a host computer or mechanism (usually an application program) on a network node which performs specialised functions on a network. One such function is to provide network security. Security is provided between a private and public network by requiring communications (i.e., information exchanges) to pass through the proxy. Another function of a proxy is to store or cache recently accessed information (i.e., copies of documents and images). If a browser desires information which is located outside the local network, that is to say on an information source attached to an external network, communications pass from the browser through the proxy before going on to the external network. Thus a proxy may operate to deny access to a private network from a public network by not replying to HTTP commands received from the public network.

[0042] Files are stored at various information sources. A user can access files from an information source, if authorised, by connecting to a computer network and requesting the files for viewing or downloading. Financial transactions are provided for over the computer network. Typically, financial transactions utilise proxies, SSL, data encryption etc.

[0043] Glossary of Terms: B2B Business to Business BOS Back Office System Convenience Includes Convenience Retailers, Fast Moving marketplace Consumer Goods (FMCG) Manufacturers, Wholesalers and Logistics Providers, Service Providers Connectivity The ability to efficiently transfer data/information Development software A software platform providing the framework for an embodiment of the present invention eBPP Electronic Bill Presentment and Payment ERP Enterprise Resource Planning FMCG Fast Moving Consumer Goods Independent A Convenience Retailer not belonging to a Convenience group of Retailers Retailers Internet Portal A web-site positioned as an entrance in the Internet to a service or variety of services Organised A Convenience Retailer belonging to a group of Convenience Retailers Retailers Participants Include Retailers, FMCG Manufacturers, Wholesalers/Logistics Providers and Service Providers POS Point of Sale Scanner Device used to obtain information/data associated with a particular product or good Specialty Stores Retailer having a specialised range of goods Supply Chain Hierarchy of movement of goods within the convenience marketplace Third Party Software Additional software ancillary to the development software required for an embodiment of the present invention Virtual Private A secure shared network, eg. secured by Network encryption, tunnelling, firewalls etc.

[0044] This identifies a need for a new type of method of, system for, or computer readable medium of instructions for, providing a new type of Internet based business to business portal for the convenience marketplace which overcomes or at least ameliorates the problems and limitations inherent in the prior art.

DISCLOSURE OF INVENTION

[0045] Broadly, the present invention provides an Electronic Marketplace Solution (EMS) which may be embodied, in part or in whole, as a method, system or computer readable medium of instructions.

[0046] The present invention seeks to provide a business to business Internet portal, which may be independent, serving companies operating within the convenience marketplace, for example within Australia and New Zealand, specifically the present invention seeks to increase operational efficiency and effectiveness for all, or at least some, participants.

[0047] In a non-limiting embodiment of the present invention, the present invention seeks to provide an Internet portal to deliver the opportunity for significant business improvement to, inter alia:

[0048] Independent Convenience Retailers through the provision of a single system, method, and/or an electronic marketplace solution to sell, buy and pay for goods/services and manage their business more effectively; and/or

[0049] Organised Convenience Groups, by providing them access to improved network management, the ability to ensure compliance and the ability to reduce costs; and/or

[0050] FMCG Manufacturers in the areas of secondary supply chain efficiencies, improved business intelligence and direct access to Convenience Retailers; and/or

[0051] Wholesalers/Logistics Providers, for reduced costs and improved efficiency and enabling them to expand their customer base; and/or

[0052] Service Providers, by enabling them to more efficiently reach a large target market.

[0053] In a preferred embodiment, the present invention seeks to provide an electronic marketplace solution which takes sales-based orders through to a shopping cart function for web-based order processing, which includes:

[0054] Point of Sale (POS) scanning, that is sales information capture;

[0055] Calculation of a replenishment order based on sales;

[0056] Electronic transfer of store order to a web ordering site; and

[0057] Integration of a store order to web-based browse and buy functionality.

[0058] In another preferred embodiment, the present invention seeks to provide an electronic marketplace solution which integrates:

[0059] Available To Promise (ATP) checking from supplier's inventory database;

[0060] Electronic transfer of checked order to supplier's order capture system,

[0061] Supplier confirmation of order acceptance and fulfilment; and

[0062] whereby links between the electronic marketplace solution's browse and buy functionality and the supplier's sales systems are provided, enabling online tracking of web-placed orders.

[0063] In a further preferred embodiment, the present invention seeks to provide an electronic marketplace solution which integrates:

[0064] Sales-based orders being placed through to a shopping cart function for Web-based order processing, including:

[0065] Point of Sale (POS) scanning;

[0066] Calculation of a replenishment order based on sales;

[0067] Electronic transfer of store order to a web ordering site; and

[0068] Integration of a store order to web-based browse and buy functionality; and

[0069] ATP checking from supplier's inventory database;

[0070] Supplier confirmation of order acceptance and fulfilment;

[0071] Electronic transfer of checked order to supplier's order capture system; and

[0072] whereby links between the electronic marketplace solution's browse and buy functionality and the supplier's sales systems are provided, enabling online tracking of web-placed orders.

[0073] In a further particular embodiment of the present invention, electronic processing of claims is integrated in the electronic marketplace solution. Preferably, but not necessarily, the electronic marketplace solution includes a centrally managed data library which is linked with the order processing system; Also, POS/BOS data can be managed within a central service, thereby increasing the accuracy of information across retail stores as well as reducing retail store level administration requirements. In a particular embodiment of the present invention, the data is managed to deliver valued information to all or some of the marketplace solution members, that is, for example, manufacturers, store owners, wholesalers and logistics providers to the retail trade. Preferably, the electronic marketplace solution can provide access to this managed information relating to consumer purchases via a business-to-business web portal. In a particular embodiment of the present invention, it is sought to provide a web-site for the Logistics Providers to access information pertaining to the targeted Retailers.

[0074] In a further embodiment of the present invention, there is provided an integrated system for providing an electronic marketplace solution, the integrated system including:

[0075] means for Point of Sale (POS) scanning of goods and associated data capture by a Convenience Retailer;

[0076] means for determining a replenishment order for goods, based on sales by the Convenience Retailer, preordained Convenience Retailer criteria, or the Convenience Retailer manually selecting goods;

[0077] means for the electronic transfer of the replenishment order to a Supplier Internet-based ordering system; and

[0078] means for integration of the replenishment order to Internet-based browse and buy functionality on the Supplier Internet-based ordering system.

[0079] In a further embodiment of the present invention, there is provided an integrated system for providing an electronic marketplace solution, the integrated system including:

[0080] means for the electronic transfer of a Convenience Retailer's replenishment order of goods to a Supplier's ordering capture system;

[0081] means for Available To Promise (ATP) checking from the Supplier's inventory database;

[0082] means for providing electronic confirmation from the Supplier of replenishment order acceptance to the Convenience Retailer; and

[0083] means for electronic tracking of replenishment orders until delivery of the goods to the Convenience Retailer.

[0084] In a further embodiment of the present invention, there is provided a system for providing an electronic marketplace, the system including:

[0085] means for a Convenience Retailer to search and browse a multiple Supplier goods and pricing catalogue;

[0086] means to provide the Convenience Retailer with online order placement, tracking and management of goods;

[0087] means to generate customised reports; and

[0088] means for electronic bill presentation and payment.

[0089] According to another possible aspect, means are also provided to facilitate Supplier access to marketplace based promotions is provided. Also the system may include a telecommunications infrastructure providing: a secure private network; a secure connection via the Internet; and Internet connectivity. According to another aspect, the system includes Point of Sale (POS) scanning of goods, and inventory management and business reporting tools for the Convenience Retailer.

[0090] In a further possible form, the system is integrated with Supplier enterprise resource planning (ERP) systems to provide:

[0091] Available To Promise (ATP) checking from the Supplier's inventory database;

[0092] credit and payment status checking from the Supplier's financial database;

[0093] electronic transfer of orders to the Supplier's order capture system; and

[0094] Supplier confirmation of order acceptance and fulfilment. Preferably, the system communicates with commercial banking systems to provide electronic payment and funds transfer facilities.

[0095] In a further embodiment of the present invention, there is provided a method of providing an electronic marketplace solution, the method including the steps of:

[0096] a Convenience Retailer identifying, on a Convenience Retailer terminal, goods which the Convenience Retailer desires to purchase, via a computer network portal, the goods being offered by a Supplier on a Supplier ordering system;

[0097] the Convenience Retailer requesting, on the Convenience Retailer terminal, the purchase and delivery of the goods;

[0098] a request being transmitted, by the Convenience Retailer terminal via the computer network, to the Supplier ordering system for the requested goods;

[0099] an automated request being transmitted, by the Convenience Retailer terminal or the Supplier ordering system, to a Logistics Provider to effect delivery of the goods; and

[0100] the Logistics Provider arranging delivery of the goods to the Convenience Retailer, whereby the Convenience Retailer terminal can be used to access goods delivery status information on a database.

[0101] In a further embodiment of the present invention, there is provided a network based business to business Internet portal, the Internet portal facilitating network communication between:

[0102] a Convenience Retailer; and

[0103] a Supplier; and

[0104] a Wholesaler or Logistics Provider; and whereby, the Internet portal is used to allow functions including:

[0105] the Convenience Retailer to order and pay for goods or services; and

[0106] the Supplier to confirm the availability of goods; and

[0107] the Logistics Provider to provide tracking of goods delivery status.

[0108] In a further embodiment of the present invention, there is provided a set of computer readable medium of instructions for use in providing an electronic marketplace solution, the set of instructions enabling web-based order processing and including procedures for: Point of Sale (POS) scanning of goods at a Convenience Retailer; calculation of a replenishment order based on sales by the Convenience Retailer; electronic transfer of the replenishment order to a web-based ordering site; and web-based browse and buy functionality for Convenience Retailer's goods orders.

[0109] In a further embodiment of the present invention, there is provided a set of computer readable medium of instructions for use in providing an electronic marketplace solution, the set of instructions enabling web-based order processing and including procedures for: Available To Promise (ATP) checking from a Supplier's inventory database; electronic transfer of orders from a Convenience. Retailer to the Supplier's order capture system; and Supplier confirmation of order acceptance.

[0110] Preferably, the computer network is the Internet. Also preferably, each terminal is a PC. In a further embodiment of the present invention all transactions, purchases and the like are stored for subsequent access. In a further embodiment of the present invention all goods are scanned by a scanner connected to the Convenience Retailer's terminal when received by the Convenience Retailer, thereby updating relevant records for any of the participants. In still a further embodiment of the present invention all goods are scanned by a scanner connected to the Convenience Retailer's terminal when purchased by a consumer from the Convenience Retailer, thereby updating relevant records for any of the participants. In an embodiment of the present invention, relevant records include: inventory information; sales figures; time of sale; place of sale; identifying information about the consumer; and/or the like. In a further broad form of the present invention, the present invention also provides that information pertaining to consumer purchases gathered by the Convenience Retailer is visible to the FMCG Manufacturer; Wholesaler; Logistics Provider; and/or Service Provider. In still a farther embodiment of the present invention, automated ordering of goods by the Convenience Retailer's terminal occurs when database records indicate that the Convenience Retailer's stock of goods is at a predetermined level. In still a further embodiment of the present invention, the FMCG Manufacturer, Wholesaler, Logistics Provider, and/or Service Provider, can individually or cooperatively collate orders for goods from Convenience Retailer's so that the distribution of goods is efficiently carried out. In still yet a further broad form, the present invention provides that any or all of the participant's terminals reside in a private network and/or access to the computer network portal occurs via a proxy server which may require user authentication. In still yet a further broad form, the present invention provides that data, information and/or files pertaining to past transactions in the convenience marketplace are available, via a computer network, to authorised users or participants from at least one information source.

[0111] In yet a further broad form, the present invention provides that the computer network can be any network of two or more communicating computers or terminals including but not limited to, an internetwork, an intranetwork, a LAN, a WAN, or the Internet. In still yet a further broad form, in accordance with the present invention information or data is exchanged by means including but not limited to: metallic cables; semi-conducting cables; optical fibre cables; satellite links; electromagnetic waves; microwave links; exchanging of memory devices; or any other such medium or combination thereof connected to a network infrastructure.

BRIEF DESCRIPTION OF FIGURES

[0112] The present invention will become apparent from the following description, which is given by way of example only, of a preferred but non-limiting embodiment thereof, described in connection with the accompanying figures, wherein:

[0113]FIG. 1 illustrates a preferred embodiment of the present invention wherein, the figure shows a broad schematic of the interaction between participants;

[0114]FIG. 2 illustrates a preferred embodiment of the present invention wherein, the figure represents the key functionality and benefits for both Independent and Organised Convenience stores;

[0115]FIG. 3 illustrates a preferred embodiment of the present invention wherein, the figure represents the key functionality and benefits for the Supplier group which includes FMCG Manufacturers, Wholesaler/Logistics Providers and Service Providers;

[0116]FIG. 4 illustrates further aspect of the functionality of an embodiment of the present invention;

[0117]FIG. 5 illustrates the software architecture of a preferred embodiment of the present invention;

[0118]FIG. 6 illustrates the key data flows associated with the business exchange of a preferred embodiment of the present invention;

[0119]FIG. 7 illustrates a schematic for Catalogue Search and Browse;

[0120]FIG. 8 illustrates a schematic for Catalogue Maintenance: Master Catalogue and Associated Views;

[0121]FIG. 9 illustrates a schematic for Catalogue Maintenance: Maintain Promotions;

[0122]FIG. 10 illustrates a schematic for Catalogue Maintenance: Maintain Pricing;

[0123]FIG. 11 illustrates a schematic for Catalogue Maintenance: Maintain My List;

[0124]FIG. 12 illustrates a schematic for Catalogue Maintenance: Maintain Frequently Ordered List;

[0125]FIG. 13 illustrates a schematic for Catalogue Maintenance: Maintain Company List;

[0126]FIG. 14 illustrates a schematic for Context Diagram: Order Capture—Saved Shopping Cart;

[0127]FIG. 15 illustrates a schematic for Context Diagram: Order Capture—Top-Up Order (Quick);

[0128]FIG. 16 illustrates a schematic for Context Diagram: Order Capture—HOS Generated Order (Aggregated Order);

[0129]FIG. 17 illustrates a schematic for Context Diagram: Order Capture—BOS Generated Order for a Single Store;

[0130]FIG. 18 illustrates a schematic for Context Diagram: Available to Promise;

[0131]FIG. 19 illustrates a schematic for Context Diagram: Community, Version 5;

[0132]FIG. 20 illustrates a schematic for Context Diagram: Order Tracking;

[0133]FIG. 21 illustrates a schematic for Context Diagram: Claims & Returns;

[0134]FIG. 21 illustrates a schematic for Electronic Payment;

[0135]FIG. 23 illustrates a schematic for Cash/Cheque Payment;

[0136]FIG. 24 illustrates a schematic for Initiate User Session;

[0137]FIG. 25 illustrates a schematic for Create & Maintain User Profile & Security;

[0138]FIG. 26 illustrates a schematic for Process Flow: Maintain Master Catalogue—Supplier Adds/Updates/Deletes Product/Price/Customer Information;

[0139]FIG. 27 illustrates a schematic for Process Flow: Maintain Master Catalogue—Retailer Adds/Updates/Deletes Product/Supplier Info. in POS/BOS;

[0140]FIG. 28 illustrates a schematic for Process Flow: Retailer adds/deletes item in their list in 12 Customer Management Suite, and generate/transmits data;

[0141]FIG. 29 illustrates a schematic for Process Flow: Retailer adds/deletes item in their list in 12 Customer Management Suite, and EMS catalogue admin. generate/transmit data;

[0142]FIG. 30 illustrates a schematic for Process Flow: Import BOS Generated Order;

[0143]FIG. 31 illustrates a schematic for Process Flow: Browse & Buy;

[0144]FIG. 32 illustrates a schematic for Process Model: Pricing;

[0145]FIG. 33 illustrates a schematic for Process Flow: Content and EMS Facilitated Email Creation and Distribution;

[0146]FIG. 34 illustrates a schematic for Process Flow: Goods Receipt;

[0147]FIG. 35 illustrates a schematic for Process Flow: Updated Order Status and Data;

[0148]FIG. 36 illustrates a schematic for Process Flow: Submit and Process Claims & Returns;

[0149]FIG. 37 illustrates a schematic for New Buyer/Retailer/Group of Retailers;

[0150]FIG. 38 illustrates a schematic for New Supplier.

MODES FOR CARRYING OUT THE INVENTION

[0151] The present invention provides a new type of Internet based business to business portal. In a particular embodiment of the present invention, the present invention seeks to address the needs of participants in the Retail Convenience Store supply chain, these participants include Retailers, FMCG Manufacturers, Wholesalers/Logistics Providers and Service Providers. This is illustrated in FIG. 1, where the electronic marketplace solution includes a computer readable medium of instructions implemented as an Internet portal to enable the participants to efficiently communicate various particulars when operating in the convenience marketplace.

[0152] The present invention is designed to provide participants with a means to more effectively manage the growth and profitability of their businesses. For this to be achieved and the benefits of an exchange marketplace to be maximised, participation by a critical mass of Retailers and FMCG Manufacturers will be required. All participants should achieve benefits by subscribing to the business exchange system/method. Cost savings through process optimisation can be achieved in the areas of, for example, order capture, payment, and delivery. Real time business intelligence information and organisational efficiencies can significantly benefit network management, field sales, marketing and manufacturing. In addition, reduced administration workload will free up valuable time for participants to focus on their business.

[0153] The present invention may be applied to any convenience marketplace in the world, although various compliance changes may be required to implement the present invention these compliance changes should be considered to be encompassed by the scope of the present invention.

[0154] Participation in the business exchange system/method of the present invention can provide significant benefits. These benefits may vary depending on whether the participant is a Retailer (organised or Independent) or Supplier (FMCG Manufacturer, Wholesaler/Logistics Provider, or Service Provider). FIGS. 2 and 3 identify the functionality and benefits associated with each of these two participant groups in a preferred embodiment of the invention.

[0155] The introduction of the overall functionality, may take place progressively over a series of business releases, as shown in FIG. 4. It should be noted, however, that such a staggered release is not a requirement of the present invention. Any, or all, of the functional aspects identified in FIG. 4 may be introduced at any time or included with any version of the present invention. FIG. 4 is included to illustrate aspects of the functionality of an embodiment of the present invention, rather than a business release strategy.

[0156] In a preferred, but non-limiting, embodiment of the invention, the present invention utilises a software development platform to create a computer readable medium of instructions. In this embodiment, development software provides the necessary framework to support the present invention. The key modules of the solution of this embodiment include: Customer Management; Order Management; Demand Fulfilment; Business Intelligence; Replenishment Planner; and eBusiness Framework.

[0157] In addition to the development software, the total solution of this embodiment is dependent on a range of further software, including Electronic Bill Presentment and Payment software and an in-store Point of Sale system.

[0158] An overview of all the key modules is presented below. It should be noted that although development software and further software is described in this embodiment of the present invention, any form of creating or obtaining such software is applicable to the present invention. Numerous alternate software platforms/languages may be utilised to work the present invention.

[0159] A possible B2B solution architecture of an embodiment of the present invention is illustrated in FIG. 5. Further technical details follow:

[0160] Point of Sale:

[0161] The Point of Sale solution (POS) comprises hardware (PC, scanner and/or data capture device) and back office software, which is located within the Retailers store, and hosted software located at a centrally managed facility. At the store level, Retailers can benefit from features including scanning technology, inventory management and sales data analysis. The hosted Point of Sale software can provide Retailers with the opportunity to use a range of applications geared towards providing increased efficiency and profitability, such as a management system, centralised pricing and promotional information, supplier management capabilities, etc.

[0162] Electronic Bill Presentment and Payment:

[0163] Electronic Bill Presentment and Payment (eBPP) is a flexible web-based application which digitises the current paper based billing, payment and notification process. The main functionality enables the creation and delivery of richly formatted bills, statements or notices, and associated advertising in an electronic format. This is transmitted via the electronic marketplace solution, to Retailers, and the return payment and remittance information to the biller.

[0164] Development software:

[0165] A software component of the business exchange is developed from the development software. This solution is made up of a number of integrated modules:

[0166] Customer Management—The Customer Management (CM) module provides users with a consistent user interface, via a single web site, to manage all interactions.

[0167] Order Management—The Order Management (OM) module provides all the necessary functionalities needed for an order management system deployed in a marketplace environment. The OM provides all the necessary work flow activities associated with an order including continuous tracking of customer orders, splitting them into individual supplier specific Purchase Orders (POs) and generating Invoices against the POs.

[0168] eBusiness framework—The eBusiness framework provides a set of workflows, guidelines and rules.

[0169] Demand Fulfilment—The Demand Fulfilment (DF) module is an intelligent order-fulfilment solution, addressing the total spectrum of needs in the order-promising process.

[0170] Fulfilment server—The Fulfilment server provides collaborative order fulfilment across discrete enterprises' individual supply chains, and an interface for integrating the front-end customer applications with back-end supply chain modules.

[0171] Business Intelligence—The Business Intelligence (BI) module provides the User Interface for interacting with the management information repository.

[0172] Data Flow:

[0173] The present invention can provide Retailers and Suppliers with significant supply chain benefits in areas including product, price and promotion visibility, a state-of-the-art POS and scanning solution, electronic order placement and processing and electronic bill presentment and payment. FIG. 6 depicts the key data flows associated with the business exchange of a preferred embodiment of the present invention. In FIG. 6, the following abbreviations have been used: POS—Point of Sale; BOS—Back Office System; HOS—Head Office System.

[0174] Equipment Configuration:

[0175] Whilst the larger Convenience Organised Retailers may have the required technology to utilise the functionality of the present invention, ie. POS system and scanners, smaller independent Retailers may not have the necessary equipment.

[0176] The key equipment required by Convenience Retailers, in order to achieve certain benefits from the present invention, are scanners, PC's and connectivity to the Internet. It is also envisaged that further embodiments can provide additional functionality, such as the integration of EFTPOS card readers into the POS systems. Convenience stores may utilise existing infrastructure, requiring only connectivity to a computer network.

[0177] Further Examples

[0178] The following examples provide a more detailed outline of one embodiment of the present invention. These examples are intended to be merely illustrative and not limiting of the scope of the present invention. These examples describe “Use Case Specifications” which illustrate features of the main components or procedures of the exemplified embodiment(s). The following examples are to be read in conjunction with the FIGS. 7 to 38 which provide a visual illustration of the described embodiment(s).

[0179] Use Case Specification: <Transmit Data>

[0180] 1. Use Case Diagrams

[0181] Catalogue Maintenance: Master Catalogue and Associated Views

[0182] Catalogue Maintenance: Maintain Promotions

[0183] Catalogue Maintenance: Maintain Pricing

[0184] 2. Use Case Actors

[0185] Supplier ERP

[0186] Electronic Marketplace Solution Catalogue Staging Area

[0187] Buyer

[0188] POS/BOS

[0189] 3. Brief Description

[0190] In this use case, data is transferred from the supplier to Electronic Marketplace Solution, from the buyer to Electronic Marketplace Solution

[0191] Supplier ERP provides the following data: supplier catalogue data, user profile data, pricing data, supplier translation tables, and promotions data

[0192] The buyer from CO provides translation tables data

[0193] The supplier provides new products data, if retailer is part of the, Electronic Marketplace Solution POS/BOS installed base—data transmission is done from Electronic Marketplace Solution catalogue to the POS/BOS system using an interface

[0194] The independent retailer with their own POS/BOS system will choose the one of the two options

[0195] 4. Flow of Events

[0196] Basic Flow

[0197] Supplier transmits data in predefined format

[0198] Electronic Marketplace Solution catalogue administrator will down load the data file into the dump files in Electronic Marketplace Solution staging area

[0199] Electronic Marketplace Solution catalogue administrator sends acknowledgement after data is verified and loaded to Electronic Marketplace Solution catalogue

[0200] 4.2 Alternative Flow(s)

[0201]  Electronic Marketplace Solution catalogue administrator is not successful in down loading data files

[0202] Electronic Marketplace Solution catalogue administrator should contact the supplier/buyer to confirm data file format, and request resending the data files

[0203]  Electronic Marketplace Solution catalogue administrator transmits product update data to POS/BOS

[0204] No longer valid, Electronic Marketplace Solution will not update retailer's POS/BOS. The retailer will have to update POS/BOS before trying to add or order an item in Electronic Marketplace Solution

[0205] Buyer's saved list is updated in Customer Management (CM)

[0206] Electronic Marketplace Solution catalogue administrator sends notification message to buyer

[0207] Electronic Marketplace Solution catalogue administrator will generate buyer specific product update files

[0208] Electronic Marketplace Solution catalogue administrator transmits this data to the buyer

[0209] Buyer updates POS/BOS system

[0210]  Data transmission between Electronic Marketplace Solution and Electronic Marketplace Solution Managed POS/BOS

[0211] Retailer initiates a POS/BOS session

[0212] POS/BOS product master file is updated based on feed from the Electronic Marketplace Solution catalogue

[0213] POS/BOS product master file is now synchronised with the retailers list/cart in the Electronic Marketplace Solution CM

[0214]  Data transmission between Electronic Marketplace Solution and CO POS/BOS

[0215] CO POS/BOS is updated

[0216] CO transmits translation table data for Supplier ID's/Product Information

[0217] CO/Electronic Marketplace Solution systems administrator updates translation tables

[0218]  Data transmission between Electronic Marketplace Solution and small retailers with independent POS/BOS systems

[0219] This group will have to choose between the data transmission flow for Electronic Marketplace Solution Managed POS/BOS, or CI POS/BOS

[0220] 5. Special Requirements

[0221] Release 1

[0222] Electronic Marketplace Solution Catalogue Staging area has to be developed to receive the supplier/buyer data (directory structure for pilot)

[0223] Data needs to be formatted based on Electronic Marketplace Solution's predefined standard

[0224] Data transmission medium should be fast and secure, to ensure that data transmitted is not corrupted

[0225] Basic scripts to automate the process of generating data files within Electronic Marketplace Solution

[0226] Transmission protocol has to be established with the supplier/buyer, if Electronic Marketplace Solution receives/sends data files via FTP

[0227] Basic scripts to validate add/update/delete data

[0228] Release 3

[0229] Scripts to automate the process of generating data files within Electronic Marketplace Solution

[0230] Scripts to validate add/update/delete data

[0231] Multi-enterprise catalogue functionality

[0232] Develop download button for buyers to generate a flat file that contains data on new items. This will save the Electronic Marketplace Solution catalogue administrator from having to generate and send data files to buyer to update POS/BOS. (no longer necessary because Electronic Marketplace Solution will not be responsible for updating POS/BOS system with new product information)

[0233] Phase 1

[0234] Develop interface between Electronic Marketplace Solution catalogue in CM and the Electronic Marketplace Solution managed POS/BOS system to synchronise the product master file and the Electronic Marketplace Solution catalogue

[0235] Develop translation tables between CI supplier/product data in the Electronic Marketplace Solution system, and the associated scripts to maintain/verify/load data

[0236] 6. Pre-Conditions

[0237] Supplier/buyer/Electronic Marketplace Solution catalogue administrator has generated flat file. For example: product, user profile, pricing, and promotion data

[0238] Electronic Marketplace Solution catalogue staging area has been set up with the required tables and associated attributes

[0239] Data load, extraction, and verification scripts have been developed

[0240] Electronic Marketplace Solution data formats have been established

[0241] 7. Post-Conditions

[0242] Data has been down loaded to the dump files in the Electronic Marketplace Solution catalogue staging area

[0243] Electronic Marketplace Solution catalogue administrator has sent acknowledgement to the supplier/buyer after successful down load, verification, and load into CM

[0244] 8. Data Requirements

[0245] User profile attributes. Still to be defined

[0246] Product Data

[0247] Supplier SKU Number

[0248] APN Number

[0249] Description

[0250] Short Description

[0251] Base UOM

[0252] Buy UOM

[0253] Packaging Information

[0254] Effectivity Dates (For New Products)

[0255] Flag (New, Update, Delete)

[0256] Product obsolete flag

[0257] Promotion Data

[0258] APN Number

[0259] Supplier SKU Number

[0260] Promotion Effectivity Date (To-From)

[0261] Discount

[0262] Min Order Qty

[0263] Max Order Qty

[0264] Promotion Details

[0265] Pricing

[0266] Supplier ED

[0267] Customer ID

[0268] APN Number

[0269] Nett Price

[0270] Field to identify add/update/delete

[0271] 9. Interfaces

[0272] Supplier/buyer will transmit the data based on their schedule. Based on the infrastructure the data file could be transmitted using FTP, e-mail attachment, or using an interface with the supplier's ERP system or the buyer's BOS/POS. The frequency of the data transmission will be done on a nightly batch process

[0273] Develop interface between Electronic Marketplace Solution catalogue in CM and the Electronic Marketplace Solution managed POS/BOS system to synchronise the product master file and the Electronic Marketplace Solution catalogue

[0274] Use Case Specification: <Update Lists>

[0275] 1. Use Case Diagrams

[0276] Catalogue Maintenance: Master Catalogue and Associated Views

[0277] 2. Use Case Actors

[0278] Customer Management

[0279] Electronic Marketplace Solution Catalogue Administrator

[0280] 3. Brief Description

[0281] Once the supplier catalogue has been updated with the new products and/or promotions, and the supplier has provided the data on the general/specific user profile they would like to push their new products and/or promotions. The Customer Management Suite should update the buyer's saved lists.

[0282] For an existing item on a retailer list, if it is on promotion then the price for that item should be updated

[0283] For promotional sku's generated by the supplier, since they do not exist on the retailer list will not be pushed but will be added to the hot deals page

[0284] 4. Flow of Events

[0285] 4.1 Basic Flow

[0286] Supplier sends the product, promotions, and user profile data

[0287] Electronic Marketplace Solution Catalogue Administrator loads the data to the supplier catalogue, in the respective category, i.e. new products in the new products category, and the promotions in the promotions category

[0288] The Electronic Marketplace Solution catalogue administrator during the load data process would have automated the process to push items to the respective buyer's list by updating the users profiles

[0289] Electronic Marketplace Solution catalogue administrator generates new products or new promotions alert

[0290] The buyer logs in and views the alert with regards to the new products/promotions based on profile

[0291] Buyers, based on user profile, access saved lists and add/delete items

[0292] 4.2 Alternative Flow(s)

[0293]  Buyer does not have correct access to view new products/promotions

[0294] Either the user profile for the buyer has not been updated to reflect the correct access for those items, in which case the catalogue administrator should be able update their profile

[0295] 5. Special Requirements

[0296] Release 1

[0297] Semi-automated alerts should be generated to notify buyers about new/promotions products

[0298] User should have the ability to add new products to their lists from the Electronic Marketplace Solution website

[0299] Automatically delete catalogue items once the end date passes. Item will be deleted from saved lists/carts if no longer on master catalogue file

[0300] Semi-automated process by which items are pushed to the retailer list/cart

[0301] Release 3

[0302] New/Promotional products should be highlighted (high priority, release 3)

[0303] Alerts should be automatically generated to notify the buyers about new/promotional products

[0304] The respective shopping lists should be updated automatically based on the user profile provided by the supplier.

[0305] Promotion item is pushed to buyer's saved lists/carts if the item is already on the list at regular price. There are issues surrounding the “how” because promotions are often based on effective dates.

[0306] Scripts to automate process of updating lists

[0307] Multi-enterprise catalogue functionality

[0308] Phase 1

[0309] Develop interface between Electronic Marketplace Solution catalogue and the Electronic Marketplace Solution managed POS/BOS system to synchronise the product master file in POS/BOS with the retailers saved list/cart in CM

[0310] Develop translation tables to synchronise the product master file in CO POS/BOS with their saved list/carts in CM. Update data file will be transmitted to the system administrator at the CO POS/BOS, and they have the option to accept/reject those changes

[0311] 6. Pre-Conditions

[0312] Supplier data on new/promotional products has been successfully loaded into the catalogue

[0313] User profiles have been updated to reflect their ability to access/add these products to their lists

[0314] 7. Post-Conditions

[0315] Buyers have updated lists.

[0316] 8. Data Requirements

[0317] User profile data

[0318] New product catalogue data

[0319] Promotion data

[0320] 9. Interfaces

[0321] Develop interface between Electronic Marketplace Solution catalogue and the Electronic Marketplace Solution managed POS/BOS system to synchronise the product master file in POS/BOS with the retailers saved list/cart in CM

[0322] Develop translation tables to synchronise the product master file in CO POS/BOS with their saved list/carts in CM

[0323] Use Case Specification: <Load/Maintain Data>

[0324] 1. Use Case Diagrams

[0325] Catalogue Maintenance: Master Catalogue and Associated Views

[0326] Catalogue Maintenance: Maintain Promotions

[0327] Catalogue Maintenance: Maintain Pricing

[0328] 2. Use Case Actors

[0329] Customer Management

[0330] Electronic Marketplace Solution Staging Area

[0331] Buyer

[0332] 3. Brief Description

[0333] This use case describes the process of loading/maintaining in the CM. After data is verified, Electronic Marketplace Solution catalogue administrator will load the data from the Electronic Marketplace Solution catalogue staging area into the CM system. This process could be used to load the supplier catalogue data, user saved list data, user profile data, pricing data, promotion data, supplier/buyer translation table data.

[0334] 4. Flow of Events

[0335] Basic Flow

[0336] The Electronic Marketplace Solution catalogue administrator has run the verification script

[0337] The Electronic Marketplace Solution catalogue administrator starts the script to load the data from the Electronic Marketplace Solution staging area to the CM suite

[0338] When the load run is complete, the Electronic Marketplace Solution catalogue administrator reviews the log file to validate the number of records loaded, and the number of records that were rejected

[0339] The different data streams get loaded to their respective tables, i.e. price cube, supplier's catalogue, promotion summary page, and the translation tables

[0340] An exception report is generated indicating records that were not loaded and the reason for the record failure

[0341] The basic flow applies to the following:

[0342] Product data into supplier catalogues (updates, new products, promotions)

[0343] Price cube

[0344] Promotion summary page

[0345] Supplier/Buyer translation tables

[0346] Alternative Flow(s)

[0347]  The Customer Management is unable load the file

[0348] Error message should be transmitted to Electronic Marketplace Solution catalogue administrator

[0349] Electronic Marketplace Solution catalogue administrator should review file and resolve issue

[0350] Electronic Marketplace Solution catalogue administrator reloads data

[0351]  The buyer sends file of new items, entered in POS/BOS

[0352] Buyer has added a new item to their POS/BOS system

[0353] Buyer transmits file containing new items added to their POS/BOS system

[0354] Buyer notifies Electronic Marketplace Solution administrator of pending data transfer

[0355] Electronic Marketplace Solution administrator runs script to load data into buyer's specific list, only if the item is part of the Electronic Marketplace Solution catalogue

[0356] An exception report is generated indicating records that were not loaded and the reason for the record failure

[0357]  Updating buyer profiles

[0358] The Electronic Marketplace Solution catalogue administrator has updated the supplier catalogue (product updates, new items, promotion items)

[0359] The Electronic Marketplace Solution catalogue administrator will the run the script to update the buyer profile based on the supplier criteria

[0360] The buyers profile is updated and their saved lists now show the new/promotion products the supplier is targeting at them

[0361]  POS/BOS passes suggested order list to Electronic Marketplace Solution

[0362] POS/BOS generates list

[0363] Electronic Marketplace Solution systems generate a PO for suppliers in Electronic Marketplace Solution catalogue

[0364] Electronic Marketplace Solution person manually orders items from suppliers that are not in Electronic Marketplace Solution catalogue (note: for pilot only)

[0365] 5. Special Requirements

[0366] Release 1

[0367] Electronic Marketplace Solution staging area will need to be developed. Directory structure for release 1

[0368] Enable products based on start and end dates. Develop product effectivity date functionality, this will allow products to be viewed between their start and end dates

[0369] Data should be loaded in a batch process, and not one item at a time

[0370] Basic script to generate error file for exception handling

[0371] Basic scripts to load data to catalogue (basic scripts, semi-automated)

[0372] Scripts to update translation tables (basic scripts, semi-automated for pilot)

[0373] Develop the custom price cube, and the scripts to load the data (we will need to develop the data model)

[0374] Release 3

[0375] Multi-enterprise catalogue functionality

[0376] Staging area to verify data and begin load to CM.

[0377] When loading supplier catalogue data, the new products or promotions should be pushed to the buyer's saved lists based on user profile information. This process has to be automated (multi-enterprise catalogue functionality) (Manual process for pilot)

[0378] Automate the process to load data into CM tables

[0379] Seamless process

[0380] Script to generate error file for exception handling when loading the data. This script should incorporate intelligence indicating what caused the data to be rejected or why certain records failed

[0381] Error message should be sent to Electronic Marketplace Solution catalogue manager when data cannot be loaded. The message should include error codes.

[0382] Scripts to load data in supplier catalogue, buyer specific list, etc., based on user profile Scripts to enable maintaining user profiles to automate the push of items

[0383] Scripts to update translation tables

[0384] Phase 1

[0385] To maintain the data in the retailers POS/BOS system that is managed by Electronic Marketplace Solution, an interface will be developed to synchronize the product master file and the Electronic Marketplace Solution catalogue. Thus when a retailer adds a product to their saved list/cart in CM, the change will be replicated to the POS/BOS via this interface

[0386] To maintain the data in the CO POS/BOS system, when an item is added/updated to their list/cart in CM, the CO administrator will have to add that item into their POS/130S before it can be ordered, since their system has precedence over the list/cart in CM. Once they have added an item to their POS/BOS, they will have to send the translation tables data so as to synchronize these two data files. The HOS for CO has the prerogative to accept/reject list/cart updates data

[0387] No maintenance will be performed for retailers who have independent POS/BOS, they will have to choose between the above two options

[0388] Retailers with no POS/BOS, and who do not have Electronic Marketplace Solution maintained POS/BOS system, there will be no data loads, since they will procure directly from the web interface

[0389] 6. Pre-Conditions

[0390] Data is in the correct format to be loaded into CM

[0391] Data has been verified and we have a clean set of data

[0392] Data resides in Electronic Marketplace Solution Catalogue Staging Area

[0393] Develop translation tables for Electronic Marketplace Solution and CO supplier/product data. If we enforce the rule that they provide us EAN product numbers along with the respective supplier id's, we would then have to only maintain translation tables for the supplier id's assigned by the CO POS/BOS system and the Electronic Marketplace Solution assigned supplier id's

[0394] 7. Post-Conditions

[0395] Supplier Data has been updated in Customer Management System

[0396] Buyer saved lists have been updated

[0397] Retailer profiles have been updated

[0398] Supplier/Buyer translation tables have been updated

[0399] Price cube has been updated

[0400] 8. Data Requirements

[0401] Supplier Catalogue—Product data attributes

[0402] Pricing—Supplier ID, Product ID, Customer ID, Nett Price

[0403] User Profile—attributes to be defined

[0404] Promotion's summary page—attributes

[0405] Supplier/Buyer translation table data requirements

[0406] BOS/POS data attribute

[0407] Product effective dates

[0408] 9. Interfaces

[0409] The process by which data is loaded into the system will be via a batch job; the frequency of this load will depend on when suppliers/buyers send Electronic Marketplace Solution updates

[0410] Develop interface with POS/BOS for loading suggested order

[0411] Develop interface between Electronic Marketplace Solution catalogue in CM and the Electronic Marketplace Solution managed POS/BOS system to synchronize the product master file and the Electronic Marketplace Solution catalogue.

[0412] Use Case Specification: <Maintain Electronic Marketplace Solution/Supplier/Buyer Translation Tables>

[0413] 1. Use Case Diagrams

[0414] Catalogue Maintenance: Master Catalogue and Associated Views

[0415] 2. Use Case Actors

[0416] Electronic Marketplace Solution Catalogue Administrator

[0417] Customer Management

[0418] 3. Brief Description

[0419] Translation tables need to be maintained to map the different unique identifiers in the back office systems of the supplier, buyer, and Electronic Marketplace Solution. The following tables need to be maintained:

[0420] Supplier SKU—APN Number

[0421] Buyer SKU—APN Number, Buyer TUN Number

[0422] Electronic Marketplace Solution SKU—APN Number

[0423] APN Number

[0424] Supplier maintained Customer ID's—Electronic Marketplace Solution maintained Customer ID's

[0425] Buyer maintained Supplier ID's—Electronic Marketplace Solution maintained Supplier ID's

[0426] 4. Flow of Events

[0427] 4.1 Basic Flow

[0428] Electronic Marketplace Solution Catalogue Administrator requests data from each entity in the trading exchange

[0429] Electronic Marketplace Solution Catalogue Administrator loads data into the appropriate table

[0430] When an entity, for example the supplier adds a new item or maintains an existing item in their ERP, they provide Electronic Marketplace Solution with their SKU Number and the corresponding APN number in a flat file

[0431] Electronic Marketplace Solution Catalogue Administrator adds/updates the translation table in CM, if it is a new item Electronic Marketplace Solution will assign an internal identifier

[0432] 4.2 Alternative Flow(s)

[0433] Supplier adds/maintains customer in their ERP

[0434] Buyer adds/maintains item in their POS/BOS

[0435] Supplier adds/maintains an item

[0436] Buyer adds/maintains supplier in their POS/BOS

[0437] The Electronic Marketplace Solution catalogue administrator will follow the steps of the basic flow outlined above, but a different translation table will be updated depending on the action performed

[0438]  Electronic Marketplace Solution—Electronic Marketplace Solution maintained POS/BOS system

[0439] For those retailers that have Electronic Marketplace Solution maintained POS/BOS systems, we will establish the rules for how the product, and supplier information is maintained, this will to eliminate the need for translation tables, as products in the POS/BOS system will be assigned the EAN number, and the supplier of that product will be assigned the quarto supplier number in the POS/BOS

[0440]  Electronic Marketplace Solution product information—Supplier Product information

[0441] The rule has to be established that when a supplier sends us their product information, the EAN number along with the Electronic Marketplace Solution assigned id for that supplier is part of the product data file. The EAN number along with the Electronic Marketplace Solution assigned supplier id will be the unique identifier for that item, this is because a product can be procured from multiple suppliers

[0442]  Electronic Marketplace Solution product information—CO POS/BOS systems

[0443] A. For those CO POS/BOS systems that store EAN numbers, we would not need translation tables for the products since this is the industry standard, and in the Electronic Marketplace Solution catalogue we are storing the products per EAN numbers

[0444] B. For those CO POS/BOS systems that do not store EAN numbers, we would have to maintain translation tables between their SKU and the EAN in Electronic Marketplace Solution

[0445] C. For the supplier id's stored in the product master file of the CO POS/BOS system, we would have to maintain translation tables

[0446] 5. Special Requirements

[0447] Release 1

[0448] Business rules that govern the maintaining of these translation tables (data format, time, frequency)

[0449] Basic scripts to load/verify data

[0450] Translations tables will need to be custom built in the CM suite. High priority, must be in release 1 of pilot, Medium level of work

[0451] Release 2

[0452] Scripts to load/verify data into translation tables. Low priority, high level of work. Needs to be automated for release 3

[0453] Multi-enterprise catalogue functionality (note: Supplier and customer ID will still have to be maintained even after the multi-enterprise catalogue roll out for release 3)

[0454] Electronic Marketplace Solution—Electronic Marketplace Solution maintained POS/BOS system

[0455] For those retailers that have Electronic Marketplace Solution maintained POS/BOS systems, we will establish the rules for how the product, and supplier information is maintained, this will eliminate the need for translation tables, as products in the POS/BOS system will be assigned the EAN number, and the supplier of that product will be assigned the quarto supplier number in the POS/BOS

[0456] Electronic Marketplace Solution product information—Supplier Product information

[0457] The rule has to be established that when a supplier sends us their product information, the EAN number along with the Electronic Marketplace Solution assigned id for that supplier is part of the product data file. The EAN number along with the Electronic Marketplace Solution assigned supplier id will be the unique identifier for that item, this is because a product can be procured from multiple suppliers

[0458] Phase 1

[0459]  Electronic Marketplace Solution product information—CO POS/BOS systems

[0460] A. For those CO POS/BOS systems that store EAN numbers, we would not need translation tables for the products since this is the industry standard, and in the Electronic Marketplace Solution catalogue we are storing the products per EAN numbers

[0461] B. For those CO POS/BOS systems that do not store EAN numbers, we would have to maintain translation tables between their SKU and the EAN in Electronic Marketplace Solution

[0462] C. For the supplier id's stored in the product master file of the CO POS/BOS system, we would have to maintain translation tables

[0463] 6. Pre-Conditions

[0464] Each entity can provide the specified information

[0465] Translation tables have been set-up in customer management

[0466] Interface has been established to update translation tables between modules of

[0467] 7. Post-Conditions

[0468] Translation tables are in synch with the different back office systems

[0469] 8. Data Requirements

[0470] APN Number

[0471] Supplier maintained Customer ID's

[0472] Electronic Marketplace Solution maintained Customer ID's

[0473] Buyer maintained Supplier ID's

[0474] Electronic Marketplace Solution maintained Supplier ID's

[0475] Supplier SKU Number

[0476] Buyer SKU Number

[0477] Electronic Marketplace Solution assigned internal number

[0478] Buyer TUN Number

[0479] 9. Interfaces

[0480] POS/BOS to Electronic Marketplace Solution

[0481] Electronic Marketplace Solution to supplier

[0482] Between modules of

[0483] Use Case Specification: <Generate Message>

[0484] 1. Use Case Diagrams

[0485] Catalogue Maintenance: Master Catalogue and Associated Views

[0486] 2. Use Case Actors

[0487] Electronic Marketplace Solution Catalogue Administrator

[0488] Customer Management

[0489] 3. Brief Description

[0490] This use case describes the process of generating and sending the “Alert” message to inform users when Electronic Marketplace Solution receives new supplier data (new products or promotions). CM will generate an “Alert” message that the user will see on the Electronic Marketplace Solution screen. This message will inform the user that new products/promotions are available.

[0491] 4. Flow of Events

[0492] 4.1 Basic Flow

[0493] A supplier catalogue has been updated with new products and promotional products

[0494] CM determines which users should see which products based on user profile information

[0495] CM generates “Alert” message to inform users about the new supplier data

[0496] CM sends (or posts) the “Alert” message to the appropriate user's Electronic Marketplace Solution website

[0497] 4.2 Alternative Flow(s)

[0498]  The “Alert” message is not generated

[0499] The “Alert” message is not generated even though there is new supplier information that matches various user profiles

[0500] Electronic Marketplace Solution catalogue administrator should monitor the process to ensure that messages are created and sent

[0501] 5. Special Requirements

[0502] 5.1 Release 1

[0503] Semi-automated process to generate alerts and send them to buyers, this function will be performed by the catalogue administrator

[0504] 5.2 Release 3

[0505] Button in the “Alert” message that will take the user directly to the list of new products or hot deals (low priority, release 3)

[0506] “Alert” messages automatically generated and sent to users based on the user profile. Note: Automating this process would be simple for a general message to all users, but very difficult to customize, based on user characteristics.

[0507] 6. Pre-Conditions

[0508] Supplier has submitted new product data or promotions data

[0509] Electronic Marketplace Solution catalogue administrator was able to load new data in Electronic Marketplace Solution catalogue

[0510] User profile gives access to user to view new products and promotions

[0511] New products/promotions summary page has been set up

[0512] User profiles have been updated

[0513] Saved lists have been updated

[0514] 7. Post-Conditions

[0515] User receives “Alert” message informing them of new products or promotions

[0516] 8. Data Requirements

[0517] Product attributes

[0518] User profile attributes

[0519] Pricing attributes

[0520] Promotion attributes

[0521] Message Details

[0522] 9. Interfaces

[0523] Use Case Specification: <Generate Frequently Ordered List>

[0524] 1. Use Case Diagrams

[0525] Catalogue Maintenance: Maintain Frequently Ordered List

[0526] 2. Use Case Actors

[0527] Buyer

[0528] Order Management Suite or POS

[0529] 3. Brief Description

[0530] This use case describes the vision of generating a frequently ordered list based on PO history. This list would include frequently ordered products and quantities. The PO history would be extracted from Electronic Marketplace Solution or from the retailer's POS/BOS. The frequently ordered list could be generated by clicking on a button in the Electronic Marketplace Solution website. PO history is analyzed and the frequently ordered list is generated. The buyer can review the list, modify the list, and/or make the list into an order.

[0531] 4. Flow of Events

[0532] 4.1 Basic Flow

[0533] Buyer initiates new session

[0534] Buyer decides to generate a frequently ordered list

[0535] Buyer click on button to generate list based on PO history

[0536] CM accesses PO history to generate the frequently ordered list

[0537] List is displayed in web user interface

[0538] Buyer reviews list

[0539] Buyer may modify list, save list, and/or make the list into an order

[0540] 4.2 Alternative Flow(s)

[0541]  Buyer would like to delete an item from the Frequently Ordered List

[0542] Buyer opens his saved frequently ordered list

[0543] Buyer selects item to delete

[0544] Buyer clicks on “Delete Item” button

[0545] CM removes item from buyer's frequently ordered list

[0546] CM save changes to frequently ordered list

[0547] 5. Special Requirements

[0548] 1. Release 1

[0549] User will manually update the frequently ordered list for pilot. With in CM a use can develop different saved carts that are essentially their frequently ordered list. Work around: It may be possible to treat the Frequently Ordered List similar to the suggested order list. The buyer would than be able to make the frequently ordered list an order or keep it as a saved cart

[0550] The Buyer should be able to modify the frequently ordered list

[0551] The Buyer should be able to save the cart and access it in the future

[0552] Buyer should be able to make the frequently ordered list into an order

[0553] 2. Release 3

[0554] Generate the frequently ordered list, based on PO history that is stored in either POS/BOS or in the order management system in Electronic Marketplace Solution. To automate this process we would have to build custom scripts based on some rules that would look at the different PO's and then generate the list

[0555] 6. Pre-Conditions

[0556] Buyer initiates new session

[0557] Supplier catalogue has been maintained

[0558] User profiles have been set-up

[0559] There is PO history available to generate the frequently ordered list

[0560] A button has been created that will generate a frequently ordered list based on PO history when a buyer clicks on it

[0561] Business rules to generate the frequently ordered list have been established and maintained

[0562] 7. Post-Conditions

[0563] Buyer has created a frequently ordered list

[0564] Buyer can view the frequently ordered list

[0565] Buyer can added an item to the frequently ordered list

[0566] Buyer can deleted an item on the frequently ordered list

[0567] Buyer can change a quantity on the frequently ordered list

[0568] Buyer can save the frequently ordered list

[0569] 8. Data Requirements

[0570] Catalogue data requirements

[0571] PO history from Electronic Marketplace Solution or POS/BOS

[0572] Business rules for generating and maintaining frequently ordered list

[0573] User profile requirements

[0574] 9. Interfaces

[0575] If frequently ordered list is generated based on PO history from retailer's POS/BOS, CM would need to interface with POS/BOS.

[0576] Use Case Specification: <Verify Data>

[0577] 1. Use Case Diagrams

[0578] Catalogue Maintenance: Master Catalogue and associated Views

[0579] Catalogue Maintenance: Maintain Promotions

[0580] Catalogue Maintenance: Maintain Pricing

[0581] 2. Use Case Actors

[0582] Electronic Marketplace Solution Catalogue Administrator

[0583] Electronic Marketplace Solution Catalogue Staging Area

[0584] 3. Brief Description

[0585] In this use case the Electronic Marketplace Solution catalogue administrator starts the verification scripts to ensure that the supplier/retailer data has been formatted to the Electronic Marketplace Solution standard. The scripts should ensure that referential integrity is maintained. The Electronic Marketplace Solution catalogue administrator will generate a list of those records that fail. The output of this step is to have clean data before loading CM suite.

[0586] 4. Flow of Events

[0587] 4.1 Basic Flow

[0588] Electronic Marketplace Solution catalogue administrator has loaded data files into the dump tables in Electronic Marketplace Solution catalogue staging area

[0589] Electronic Marketplace Solution catalogue administrator runs the data verification script on the supplier/retailer provided data

[0590] On successful completion of the script, data is ready to be loaded into CM

[0591] 4.2 Alternative Flow(s)

[0592]  Verification script generates invalid data

[0593] Electronic Marketplace Solution catalogue administrator reviews data file to resolve issues

[0594] If issues are successfully resolved, data is ready to be loaded to CM suite

[0595] If issues are not resolved, Electronic Marketplace Solution catalogue administrator should run script to generate exception report

[0596] Electronic Marketplace Solution catalogue administrator should send exception report to appropriate supplier/retailer for resolution

[0597] 5. Special Requirements

[0598] 1. Release 1

[0599] Electronic Marketplace Solution has defined the different data format and integrity rules around the different reference tables, such as UOM, Category, etc.

[0600] Generate exception report scripts

[0601] Basic data verification scripts

[0602] Staging area to test data before data is loaded CM suite. (Use directory structure for pilot). Basic scripts for loading, verifying, and generating exception reports

[0603] 1. Release 3

[0604] Data verification scripts, with intelligence built into the error report detailing the reason the record failed

[0605] Multi-enterprise catalogue development

[0606] 6. Pre-Conditions

[0607] Data verification scripts have been developed

[0608] Electronic Marketplace Solution Staging Area has been set-up

[0609] Suppliers/retailers have provided files in Electronic Marketplace Solution format, and they have developed the required data extraction scripts

[0610] Script to generate exception report

[0611] Data file from the supplier/retailer has been down loaded to the Electronic Marketplace Solution staging area

[0612] Error Codes have been defined

[0613] 7. Post-Conditions

[0614] Data file has been verified, and records have been marked as accept, or reject

[0615] Exception list has been generated, and is ready to be transmitted to the supplier/retailer for resolution (if the Electronic Marketplace Solution Catalogue Administrator cannot resolve the issues)

[0616] 8. Data Requirements

[0617] Product attributes

[0618] Customer profile attributes

[0619] Pricing attributes

[0620] Promotion attributes

[0621] Error codes

[0622] Translation table data

[0623] 9. Interfaces

[0624] Use Case Specification: <Review/Resolve Exceptions>

[0625] 1. Use Case Diagrams

[0626] Catalogue Maintenance: Master Catalogue and Associated Views

[0627] Catalogue Maintenance: Maintain Pricing

[0628] Catalogue Maintenance: Maintain Promotions

[0629] 2. Use Case Actors

[0630] Electronic Marketplace Solution Catalogue Administrator

[0631] Electronic Marketplace Solution Catalogue Staging Area

[0632] Supplier ERP

[0633] Buyer

[0634] 3. Brief Description

[0635] In this use case the Electronic Marketplace Solution catalogue administrator will review the exception records that are generated once the verification scripts have been run, or for those records that were rejected during the data load process. The verification scripts will generate the list of all the records that do not match the Electronic Marketplace Solution catalogue data format. The scripts will also track those records that fail with the database integrity rules. The Electronic Marketplace Solution catalogue administrator reviews/resolves issues on exception report. If Electronic Marketplace Solution catalogue administrator is unable to correct records, the data will be sent back to the supplier/buyer for review and resolution.

[0636] 4. Flow of Events

[0637] 4.1 Basic Flow

[0638] Electronic Marketplace Solution catalogue administrator has performed either the verify data or data load process

[0639] Exception report for error records will be generated with error codes

[0640] Electronic Marketplace Solution catalogue administrator will review records, and resolve issues

[0641] If the issue can be resolved, the Electronic Marketplace Solution catalogue administrator loads data

[0642] 4.2 Alternative Flow(s)

[0643]  Electronic Marketplace Solution Catalogue Administrator cannot resolve the exceptions

[0644] The Electronic Marketplace Solution Catalogue Administrator will send the exceptions list to the respective supplier or buyer for resolution

[0645] 5. Special Requirements

[0646] 1. Release 1

[0647] Exception reports should be in a format that is acceptable to the supplier/buyer, so they can resolve the errors quickly

[0648] Data should be loaded in a batch process, and not one item at a time

[0649] Basic scripts to verify data, load data, generate exception reports

[0650] Staging area to test and hold data. (Use directory structure for pilot)

[0651] 2. Release 3

[0652] Verification scripts with intelligence to list the attribute and the error (develop basic scripts for pilot, but intelligent error reporting will be needed for release 3)

[0653] Multi-enterprise catalogue functionality, thus the supplier will be responsible for maintaining their catalogue

[0654] 6. Pre-Conditions

[0655] Data verification scripts/data load has been run

[0656] Exception report has been generated

[0657] Error codes have been defined

[0658] 7. Post-Conditions

[0659] Electronic Marketplace Solution catalogue administrator resolves the exceptions and the data is ready to load

[0660] Supplier/buyer has received the exceptions list, and is in the process of resolving the issue

[0661] 8. Data Requirements

[0662] Product attributes

[0663] Pricing attributes

[0664] Promotion attributes

[0665] User Profile attributes

[0666] Buyer translation table

[0667] BOS/POS requirements

[0668] Saved list data requirements

[0669] The exception report should have an error code field

[0670] 9. Interfaces

[0671] We need to follow up on interface details. This is still unresolved.

[0672] Use Case Specification: <Review Promotions>

[0673] 1. Use Case Diagrams

[0674] Catalogue Search and Browse

[0675] 2. Use Case Actors

[0676] Supplier

[0677] HO Category Manager

[0678] Buyer

[0679] Site Staff 1

[0680] Site Staff 2

[0681] Customer Management

[0682] 3. Brief Description

[0683] This use case describes how users, based on their user profiles, will review promotions during search, browse, and order capture activities. The user should also be able to go directly to the list of items that are on promotion by selecting the promotions summary page. The user should be able to drill down on the item to view the promotion details, such as min/max order quantity, expiration date, special packaging, discounts etc

[0684] 4. Flow of Events

[0685] 4.1 Basic Flow

[0686] The user initiates their session

[0687] The user selects the promotions summary page

[0688] The user reviews the list of items on promotion

[0689] The user clicks on the view special details button

[0690] The user is then taken to the promotions template where they can review the details

[0691] The user then has the choice of going back to the promotions list, or adding the item to their shopping cart.

[0692] 4.2 Alternative Flow(s)

[0693]  User is in the order capture process

[0694] The user is currently in the process of reviewing their order list

[0695] Those items on promotion will have an icon (for e.g. a star) to designate that they are on promotion. The user should be able to view the details on the promotion by clicking on the view special details button

[0696] The user is then taken to the promotions template, where they can either go back to the order list, or go to the edit order page to adjust the line item

[0697]  User is in the process of searching for an item

[0698] The user is currently in the process of searching for an item. The user is presented with the result set

[0699] Those items on promotion win have an icon (for e.g. a star) to designate that they are on promotion. The user should then be able to view the details on the promotion by clicking on the view promotion details button

[0700] The user is then taken to the promotions template, where they can either go back to the search page, or select the item and add it to their shopping cart

[0701] 5. Special Requirements

[0702] 5.1 Release 1

[0703] Promotion details can be accessed by clicking on the item. This is a link to a static page that contains the promotion details (the description of the promotion)

[0704] To view the promotion details, the promotion description text will have to be rendered in some format. All the promotion details, such discounts, etc. will have to be part of the promotion description

[0705] Hot deals page. Static text page for pilot

[0706] If a price changes on an item so that it is considered on promotion, the APN should remain the same. If there is some other type of change, a new APN should be created

[0707] 5.2 Release 3

[0708] Promotions are displayed when the user is performing the following functions: Search, Browse, Order Capture

[0709] Promotions can be targeted to buyers that fit the profile defied by the supplier

[0710] Set up hot deals summary page to list items from all suppliers and show items by category, by product group, by line item. The catalogue will have to be modeled to accommodate this functionality

[0711] Automate the process by which the user profile is updated to grant/deny access to a promotional item

[0712] Automating the process by which promotional items are pushed to the buyer's lists based on the profile provided by the supplier (will accept workaround for pilot, workaround is sending an alert to user about new promotions, this issue will be easier to solve with Aspect functionality that should be available in for release 3). High Priority

[0713] Set up special indicator to designate an item is on promotion during search/browse/order capture (different color indicator is preferred by Electronic Marketplace Solution). High Priority

[0714] Promotions are displayed based on start and end dates, i.e. set up effective date functionality, this will drive when the item is available to be viewed

[0715] 5.3 Phase 1

[0716] Develop rules to match promotion restrictions such as min/max order amount, effective dates, etc. when the item is added to the shopping cart

[0717] Click count on hot deals summary page, advertising banners, etc.

[0718] Since generates a unique number for items on promotions, it will be difficult for the supplier/buyer to analysis data for reporting reasons. Workaround: Electronic Marketplace Solution maintains translation tables between the regular SKU number and the Promotional SKU number

[0719] 6. Pre-Conditions

[0720] Supplier's catalogues/lists/cart/promotions summary page have been set-up

[0721] User profiles have been set-up based on supplier target market data (i.e. profiles, specific retailers)

[0722] Promotional data has been set-up based on data provided by supplier details

[0723] Promotions summary page has been set up

[0724] 7. Post-Conditions

[0725] User has reviewed promotion details

[0726] User has selected an item to add to cart

[0727] User has selected items for comparison

[0728] 8. Data Requirements

[0729] Start/End Date

[0730] APN Number

[0731] Promotion Tag Line

[0732] Discount %

[0733] Promotion Description

[0734] Min Order Amount

[0735] Max Order Amount

[0736] Target Market Profile Data

[0737] Retailer ID

[0738] 9. Interfaces

[0739] Pricing cube has been set-up in Customer Management. This price cube contains pricing per supplier, per customer, per product. The pricing data load from the supplier ERP system should be a batch load process.

[0740] Use Case Specification: <Review/Add/Delete Available Item>

[0741] 1. Use Case Diagrams

[0742] Catalogue Maintenance: Maintain Company List

[0743] Catalogue Maintenance: Maintain Frequently Ordered List

[0744] Catalogue Maintenance: Maintain My List

[0745] Catalogue Maintenance: Maintain Promotions

[0746] 2. Use Case Actors

[0747] HO Category Manager (in detailed text below, the term “buyer” includes HO Category Manager)

[0748] Buyer

[0749] Theo

[0750] Customer Management

[0751] 3. Brief Description

[0752] This use case outlines how a buyer can add products to their saved lists or cart. The following options are available:

[0753] Buyer reviews products that are available based on user profile. Buyer adds items to a saved list/cart. For example, in a convenience organized setting the HO category manager would add products to the company list. The MSF store manager would add items to my list. For convenience independent, the store manger/owner would be able to update lists.

[0754] Buyer reviews new product lists and adds items to a saved list or cart

[0755] Buyer reviews hot deals page and adds items to a saved list or cart

[0756] 4. Flow of Events

[0757] 4.1 Basic Flow

[0758] Buyer reviews products available

[0759] Buyer reviews new product lists and promotions lists

[0760] Buyer finds products to add to one of their saved lists or cart

[0761] Buyer clicks on a button next to the item to add the item to a saved list or cart

[0762] CM saves the buyer's lists/carts

[0763] The buyer can access the lists/carts in the future

[0764] The user profile has to be maintained based on the supplier provided data to limit which items a buyer can access.

[0765] 4.2 Alternative Flow(s)

[0766]  Buyer does not want to add any items to a saved list

[0767] Buyer reviews supplier catalogues, new product lists, and promotions

[0768] Buyer does not want to add any items to a saved list

[0769] Buyer should be able to exit product list without selecting items

[0770] Buyer should be able to access other Electronic Marketplace Solution screens

[0771]  Buyer would like to delete items from saved lists or cart

[0772] Buyer reviews saved list or cart to modify

[0773] Buyer selects item to delete

[0774] Buyer clicks on “delete” item button

[0775] Item is removed from saved list or cart

[0776] The list/cart is saved

[0777] 5. Special Requirements

[0778] 1. Release 1

[0779] Button that enables buyer to add item to a list/cart

[0780] Button that enables buyer to delete item from list/cart

[0781] Current functionality is acceptable, with regards to add/delete of an item

[0782] Semi-Automated process to push items based on user profile. The catalogue administrator will have to perform this function

[0783] 2. Release 3

[0784] Button or Drop down box where buyer can choose which list to add the item

[0785] Automated push of new products and promotions based on user profile. Automated generation of alert message, informing users that there are new/promotion products available. (Semi-automated process for pilot. To determine the level of automated for release 3)

[0786] 6. Pre-Conditions

[0787] Buyer initiated new session

[0788] Buyer has the appropriate profile to view items

[0789] Supplier catalogue has been updated

[0790] User profile has been set up

[0791] 7. Post-Conditions

[0792] Item is added/deleted to one of the buyer's saved lists/cart

[0793] Buyer can access other screens in Electronic Marketplace Solution instead of adding an item to a saved list

[0794] After the buyer has added an item, they need to ensure that their respective POS/BOS system has also added the same item before it can be ordered through Electronic Marketplace Solution

[0795] 8. Data Requirements

[0796] User profile

[0797] Product information

[0798] Pricing information

[0799] Promotions information

[0800] 9. Interfaces

[0801] POS/BOS needs to be updated with new product information

[0802] Use Case Specification: <Notify Community of Changes/Adds/Deletes>

[0803] 1. Use Case Diagrams

[0804] Catalogue Maintenance: Maintain Company List

[0805] 2. Use Case Actors

[0806] HO Category Manager

[0807] Customer Management

[0808] 3. Brief Description

[0809] This use case describes how the HO would notify the user community about changes, adds, and deletes to the company list. For example, when new products are available for the buyer to order or add to a saved list.

[0810] 4. Flow of Events

[0811] 4.1 Basic Flow

[0812] Electronic Marketplace Solution catalogue administrator uses a semi-automated process to send out alerts. The alerts will be generated after the Head Office has made an update that will affect a buyer's list. The alert will contain information about the update.

[0813] The buyer can act on this alert by updating saved list/cart

[0814] 4.2 Alternative Flow(s)

[0815] 4.2.1 Alerts are automatically generated

[0816] Alerts are automatically generated based on user profile

[0817] Electronic Marketplace Solution catalogue administrator would not have to manually send out alerts

[0818] 4.2.2 Buyer's lists are automatically updated

[0819] The updates are pushed out based on user profile

[0820] This automated functionality would eliminate the alert step of the use case

[0821] The automation would also eliminate the need for the buyer to manually update saved list/cart

[0822] 5. Special Requirements

[0823] 1. Release 1

[0824] Electronic Marketplace Solution catalogue administrator should be able to generate alert message to send to the user communities

[0825] 2. Release 3

[0826] Automated push of updates to buyer lists/carts

[0827] Automatic update of buyer's saved lists/cart (high priority, but will not be available until release 3, multi-enterprise catalogue)

[0828] Automated alert generation (low priority, this will be a semi-automated process for release 1)

[0829] 6. Pre-Conditions

[0830] Catalogue data has been updated

[0831] User profiles have been set-up

[0832] 7. Post-Conditions

[0833] Buyer is updated about changes

[0834] Buyer modifies saved list/cart

[0835] Buyer reviews updates

[0836] 8. Data Requirements

[0837] User profiles

[0838] Product data

[0839] 9. Interfaces

[0840] Use Case Specification: <Browse>

[0841] 1. Use Case Diagrams

[0842] Catalogue Search and Browse

[0843] 2. Use Case Actors

[0844] Supplier

[0845] HO Category Manager

[0846] Buyer

[0847] Site Staff 1

[0848] Site Staff 2

[0849] Customer Management

[0850] 3. Brief Description

[0851] This use case describes the browse function. A user can browse by a specific supplier's catalogue, and with in the different categories like, product category, promotions, or new products

[0852] The user should be able to browse based on product category (Cigarettes), and then be able to drill down into the brand group (B&H, Coca Cola), product group with in the brand group (B&H 100's)

[0853] The default browse list should be my list

[0854] The user should have the ability to change default settings to another list/catalogue

[0855] 4. Flow of Events

[0856] 4.1 Basic Flow

[0857] User initiates session

[0858] User selects the browse tab, the default browse list should be my list

[0859] The user should be able to browse by Supplier, Product, saved cart/list, or the promotions summary (hot deals page). The user clicks on the go button to retrieve the result set

[0860] User is then presented with the result set

[0861] User can select an item and add them to cart/list

[0862] User can select an item and delete it from cart/list

[0863] User can drill down on each product for more details about pricing, packaging etc.

[0864] User can select more than one item and do a comparison. User has option to add item(s) to cart/list

[0865] 4.2 Alternative Flow(s)

[0866]  User cannot find product via browsing

[0867] User cannot find desired information

[0868] User can access help functionality by clicking on the browse help tab

[0869] User can view a static help page that explains how the browse functionality works

[0870]  User chooses another cart/list/catalogue to browse

[0871] User selects a cart/list/catalogue to browse

[0872] User clicks on the go button

[0873] Results set is returned

[0874] User can perform all the functions listed in the basic flow

[0875]  User selects the promotions summary (hot deals) page

[0876] User selects the promotions summary page (hot deals page). This page lists all the products that are on promotion from the different suppliers

[0877] User selects more than one product and does a comparison

[0878] User adds item(s) to cart or continues to browse

[0879] 5. Special Requirements

[0880] 1. Release 1

[0881] Standard functionality, there will be no default browse list, as the user can choose the list/cart from the navigation bar.

[0882] User should be able to determine the default browse list. Since the current functionality is adequate for browsing, there is no default list. Standard functionality is accepted, the user can choose via the navigation bar which catalogue/list/cart they would like to browse

[0883] User should be able to browse by product category, manufacturer, and product group. we would have to, model the catalogue as a single catalogue, the hierarchy of the catalogue will be Category/Brand/Supplier/Product

[0884] User should be able to add item to the cart or to a saved list. In you can maintain only one list, but you can have multiple saved carts

[0885] System should confirm when item is added to shopping cart or saved lists. When you add an item to a list/cart, you are taken to the list/cart where the item has been added, but there is no system prompt

[0886] Hot deals summary page. This will be a static page is for release 1

[0887] Develop static page for browse help functionality. Consolidate the help functionality into one for search/browse, this will be a basic help page

[0888] Modeling for the catalogue should be in the following order: Category, Brand, Supplier, and Product

[0889] 2. Release 3

[0890] Hot deals page lists all items from different suppliers that are on promotion. Page should be set up by category, by brand, by line item

[0891] User should be able to choose the cart/list they want to add items. Current functionality is that users pick list and than adds item to it, this will be acceptable for release 1, but would like functionality for release 3

[0892] Automatic targeted promotions based on supplier provided user profiles (high level of work, not necessary for pilot, functionality should be in release 3, where by we can identify and highlight existing items that are on promotion in a particular users list/cart)

[0893] One alternative item determined by supplier (this is low priority functionality, required for release 3 implementation. The work around for this would be to have the supplier suggest an alternative item, which will be stored as an attribute for the item)

[0894] 6. Pre-Conditions

[0895] User has initiated new session

[0896] Supplier catalogue, user specified list, and shopping cart have been set-up

[0897] User profiles set up. This is how a specific user can only access certain categories in the supplier catalogue, as well as which catalogues, shopping lists, and shopping carts they have access to

[0898] Promotions information has been set up in the supplier catalogue and the user profile has been updated so that they can access the items

[0899] Promotions summary page has been set up

[0900] 7. Post-Conditions

[0901] User can drill down and has found item(s)

[0902] User can select items and add to cart or saved lists

[0903] User can start a search, by going to the search button

[0904] User can choose to browse a different list or catalogue

[0905] 8. Data Requirements

[0906] Product Name

[0907] Catalog number

[0908] Line Item number

[0909] APN number

[0910] Description

[0911] Size

[0912] Nett Price

[0913] Min/Max Order Qty (this will be an attribute of description)

[0914] Recommended Retail Price (RRP)

[0915] Promotional information

[0916] Supplier number

[0917] Packing conversion (number of each per pack)

[0918] User profile data

[0919] Supplier—Post Code table

[0920] Retailer's Post Code

[0921] Search Terms, per product. Additional product attributes; for example: retailers may call Winfield Ultra Lights as Winfield Blue

[0922] Alternative item determined by supplier (only one alternative item will be modeled)

[0923] 9. Interface Requirements

[0924] Pricing cube has been set-up in customer management. This price cube contains pricing per supplier, per customer, per product. The pricing data load from the supplier ERP system should be a batch load process. Assumption: Electronic Marketplace Solution will not calculate GST.

[0925] The price cube will also have the RRP price. This requirement is for the POS/BOS system

[0926] Use Case Specification: <Search>

[0927] 1. Use Case Diagrams

[0928] Catalogue Search and Browse

[0929] 2. Use Case Actors

[0930] Supplier

[0931] HO Category Manager

[0932] Buyer

[0933] Site Staff 1

[0934] Site Staff 2

[0935] Customer Management

[0936] 3. Brief Description

[0937] This use case describes searching across an supplier catalogues, a specific supplier catalogue, saved lists/carts, frequently ordered list, promotions summary page (hot deals page). This use case also describes searching a category within a supplier's catalogue using a parametric search (this is an attribute based search).

[0938] 4. Flow of Events

[0939] 4.1 Basic Flow

[0940] User initiates session

[0941] User selects the search button

[0942] The default search list will be company/store list

[0943] The user will have the ability to choose a different catalogue/list to search, by selecting the appropriate list from the drop down box

[0944] The user will have the ability to select the criteria to search by. Various search criteria will be listed in a drop down box (i.e. keyword, product name, mfg., etc.)

[0945] User inputs specific search terms in the search field (i.e. soda, Coke, 123456, etc.)

[0946] User clicks on submit search button

[0947] Result set is presented with the product description and nett price from the custom price cube across all suppliers with whom the retailer has trade terms

[0948] User can then add items to their list or cart

[0949] 4.2 Alternative Flow(s)

[0950]  Item not found (i.e. no results returned).

[0951] A message is displayed directing the user to the advanced search link

[0952] User can access search tips or search help

[0953] 5. Special Requirements

[0954] 1. Release 1

[0955] Standard search functionality, which encompasses key word search, and with in a category attribute search (Parametric search)

[0956] Click button to frequently ordered list. Work around is to choose the different list/carts from the navigation bar.

[0957] Searches are not case-sensitive

[0958] If you search by “co” all products beginning with “co” are returned in the result set

[0959] Search tips are available via Help functionality. This will be a basic help page

[0960] Refine search or new search options. Currently you search by key word, and use the drill down, or parametric search to refine your results, this is acceptable.

[0961] The result set presented should also list the catalogue

[0962] Ability to add item to cart or list from results page

[0963] System should confirm when item is added to shopping cart or saved lists. When you add an item to a list/cart, you are taken to the list/cart where the item has been added

[0964] Ability to click on an item and view the details

[0965] Nett price needs to be displayed based on the supplier, customer, product

[0966] User is restricted to view/search items based on user profile

[0967] When searching for an item, the result set should also return those items that are on promotion. For release 1 we are building a static page, if the item on promotion is part of the main catalogue it will be returned in the search, otherwise it will be part of the static page

[0968] Hot deals page must be available for pilot, work around is a static page or semi-automatic process of modeling a hot deals catalogue

[0969] 1. Release 3

[0970] Drop-down box to select the catalogue/list/cart to search. This not a needed, as current functionality is adequate

[0971] Ability to search on a list/cart. needs to follow-up with their development to see when this will be available

[0972] Storeowner should have the ability to set the defaults for the search functionality (i.e. default catalogue/list). This not a high priority, as current functionality is adequate

[0973] Set up the promotion summary page that lists all promotions across suppliers, grouped by product category. (high priority, automated functionality needed for release 3, where by promotions are pushed to the retailer list/cart)

[0974] Alternative/replacement product offering would need to be modeled in the Replenishment Planner module, and then need to develop solution on how to render it during search/browse (high priority)

[0975] 6. Pre-Conditions

[0976] User initiated session

[0977] User profile has been set up

[0978] The supplier catalogues/my list/shopping cart/promotion summary page (hot deals page) have been set up

[0979] Advanced search, and search tips has been set-up

[0980] Help functionality available

[0981] Supplier has set up promotions and has included expiration date and promotion detail

[0982] Pricing cube has been set-up

[0983] Interface between CM and the price cube is active

[0984] 7. Post-Conditions

[0985] Search results displayed

[0986] Item can be added to cart/list

[0987] User can choose next search or refine search

[0988] User can access the frequently ordered list

[0989] User can drill down and has found item(s)

[0990] User can access help functionality

[0991] 8. Data Requirements

[0992] Keyword

[0993] Product Name

[0994] Margin

[0995] Catalog number

[0996] Line Item number

[0997] APN number

[0998] Description

[0999] Size

[1000] Nett Price

[1001] Min/Max Order Qty (description)

[1002] Recommended Retail Price (RRP)

[1003] Promotional information

[1004] Supplier number

[1005] Packing conversion (number of each per pack)

[1006] User profile data

[1007] Supplier—Postal Code table

[1008] Retailer's Postal Code

[1009] Search Terms, per product. Additional product attributes; for example: buyers may call Winfield-Ultra Lights, Winfield Blue

[1010] Alternative item determined by supplier

[1011] 9. Interface Requirements

[1012] Pricing cube has been set-up in Customer Management. This price cube contains pricing per supplier, per customer, per product. The pricing data load from the supplier ERP system should be a batch load process.

[1013] Use Case Specification: <Maintain Catalogue Standards>

[1014] 1. Use Case Diagrams

[1015] Catalogue Maintenance: Master Catalogue and Associated Views

[1016] 2. Use Case Actors

[1017] Electronic Marketplace Solution Catalogue Administrator

[1018] Customer Management

[1019] 3. Brief Description

[1020] This use case describes the process by which, the Electronic Marketplace Solution Catalogue Administrator will maintain the following catalogue standards:

[1021] Data formats (use GCI standard)

[1022] Categories (defined by BAT for pilot)

[1023] User roles

[1024] User access levels

[1025] Store classification (use BAT classification)

[1026] UOM conversion rules—use metric (Australian) conversion rules

[1027] Reference tables: A reference table is like a look up table and is used to standardize the different values an attribute can have. For example the unit of measure reference table will contain all the allowable uom values—low priority

[1028] Promotion template

[1029] 4. Flow of Events

[1030] 4.1 Basic Flow

[1031] Electronic Marketplace Solution Catalogue Administrator gets request from supplier/buyer for add/updating a reference value

[1032] Electronic Marketplace Solution Catalogue Administrator accepts request

[1033] Electronic Marketplace Solution Catalogue Administrator updates the catalogue standards, and notifies all parties of the change

[1034] 4.2 Alternative Flow(s)

[1035] Electronic Marketplace Solution Catalogue Administrator rejects request

[1036] Electronic Marketplace Solution Catalogue Administrator informs respective party

[1037] Electronic Marketplace Solution initiates the update of its catalogue standards

[1038] Electronic Marketplace Solution Catalogue Administrator updates the catalogue standards, and notifies all parties of the change

[1039] 5. Special Requirements

[1040] 1. Release 1

[1041] Basic scripts to load reference tables if required

[1042] The Electronic Marketplace Solution catalogue staging area will require the different reference tables, and will have to be maintained by the catalogue administrator. High priority.

[1043] 2. Release 3

[1044] Scripts to automate process

[1045] Multi-enterprise catalogue functionality.

[1046] 6. Pre-Conditions

[1047] Initial set up of the data standards, and reference tables has be completed

[1048] Supplier/Buyer has initiated request to change

[1049] 7. Post-Conditions

[1050] Updated catalogue standard has been implemented

[1051] All parties have been informed of this change, and the effect it shall have when they send data that has to be loaded

[1052] 8. Data Requirements

[1053] UOM reference table attributes (all measures should be metric!)

[1054] Data formats (use GCI standards)

[1055] Standard categories (defined based on BAT for pilot)

[1056] User roles

[1057] User access levels

[1058] Store classification (use BAT classification/standards for pilot)

[1059] International standard format (GCI)

[1060] UOM should be defined in catalogue under product description for each item

[1061]  Note: Price in Electronic Marketplace Solution Catalogue is the nett price. RRP (recommended retailer's price) is handled by POS/BOS. Retailer price to consumers is out of scope for this session, but in scope for POS/BOS and Electronic Marketplace Solution operations

[1062] Additional data requirements identified during RSW:

[1063] EAN

[1064] UPC/UCC

[1065] TUN

[1066] PLU (unique)

[1067] PSEDO PLU

[1068] Same across suppliers

[1069] Used for produce items

[1070] PLU LINK primary product

[1071] 9. Interfaces

[1072] Use Case Specification: <Open Message>

[1073] 1. Use Case Diagrams

[1074] Catalogue Maintenance: Maintain Company List

[1075] Catalogue Maintenance: Maintain My List

[1076] 2. Use Case Actors

[1077] Buyer

[1078] HO Category Manager

[1079] Customer Management

[1080] 3. Brief Description

[1081] This use case describes the process of the buyer opening the “Alert” message in the Electronic Marketplace Solution website. CM will send or post an “Alert” message informing the buyer about new products, products on promotion, and/or other system messages. There should be a button on the message that will take the buyer directly to the list of new products or promotions.

[1082] 4. Flow of events

[1083] 4.1 Basic Flow

[1084] Buyer sees new message alert in Electronic Marketplace Solution website

[1085] Buyer clicks on button to open message, or the message is displayed immediately when buyer logs in

[1086] The message informs the buyer about products that are on promotion, new products, and/or other system messages

[1087] Buyer clicks on button in message that will take him directly to the new products list or promotions summary page in Electronic Marketplace Solution website

[1088] 4.2 Alternative Flow(s)

[1089]  Buyer is unable to open the new message

[1090] Buyer should access Help functionality

[1091] Buyer could send a message to system administrator

[1092] 5. Special Requirements

[1093] 5.1 Release 1

[1094] Semi-automated process of generating and sending buyer alert messages

[1095] 5.2 Release 3

[1096] “Alert” messages automatically sent to buyers based on the user profile Button in the “Alert” message that will take the buyer directly to the list of new products available or hot deals summary page (low priority, release 3)

[1097] 6. Pre-Conditions

[1098] Buyer has initiated a new session

[1099] CM has generated “Alert” message

[1100] CM successfully sent or posted the “Alert” message on the Electronic Marketplace Solution website for a particular buyer, based on user profile

[1101] User profile has been set up

[1102] 7. Post-Conditions

[1103] Buyer is able to review the message and act accordingly

[1104] Buyer can close the message and access other screens within Electronic Marketplace Solution

[1105] 8. Data Requirements

[1106] Message Details

[1107] User Profile Details

[1108] New Product Details

[1109] Promotions Details

[1110] 9. Interfaces

[1111] Use Case Specification: Check Availability

[1112] 1. Use Case Diagrams

[1113] Available to Promise

[1114] 2. Use Case Actors

[1115] Customer Management

[1116] Demand Fulfilment

[1117] 3. Brief Description

[1118] Shopping cart is sent to Demand Fulfilment and stock availability is checked.

[1119] Upon accepting the allocation, shopping cart becomes a customer order with status of Open. The customer order is split and sent into purchase orders and sent to individual suppliers.

[1120] 4. Flow of Events

[1121] 4.1 Basic Flow

[1122] Shopping cart is sent to Demand Fulfilment.

[1123] Demand Fulfilment checks stock levels for each line item (can be for multiple suppliers).

[1124] Demand Fulfilment sends shopping cart back to Customer Management with available stock information.

[1125] Buyer reviews stock allocations.

[1126] Buyer clicks Accept and shopping cart is converted to an open customer order.

[1127] Customer order is split into purchase orders.

[1128] Purchase orders are sent to individual suppliers.

[1129] 4.2 Alternative Flow(s)

[1130] 4.2.1 Desired quantity is not available and buyer accepts order anyway

[1131] When there is not enough stock in Demand Fulfilment to meet the desired quantity levels, the Buyer has the ability to still place the order.

[1132] Demand Fulfilment returns to Customer Management saying the desired quantity is not available.

[1133] Buyer clicks on Accept without adjusting quantities.

[1134] Demand Fulfilment sends the purchase order directly to the supplier.

[1135] 4.2.2 Desired quantity is not available and buyer adjusts the quantity, finds substitute products or suppliers, or deletes the line item.

[1136] When there is not enough stock in Demand Fulfilment to meet the desired quantity levels, the Buyer has the ability to change the line items on the order.

[1137] Buyer clicks on Change Order.

[1138] Buyer returns to shopping cart to add/edit/delete products and quantity (see Add to Shopping Cart use case).

[1139] 5. Special Requirements

[1140] 5.1 Usability

[1141] 5.1.1 Pilot—Release 1

[1142] Check stock levels as a memory resident batch process for multiple products for multiple suppliers

[1143] Stock allocated on first in first out (FIFO) basis

[1144] Allow buyer to purchase more quantity than what Demand Fulfilment says is available

[1145] Provide a distinction between zero quantity available and no information on quantity is available

[1146] Provide a button to Accept the allocation

[1147] Provide a button to Change Order

[1148] Send final purchase orders to suppliers

[1149] Send final customer order to BOS (Electronic Marketplace Solution customer order is synchronised with BOS purchase order)

[1150] 5.1.2 Pilot—Release 3

[1151] When desired quantity is not available, Buyer has to return to the shopping cart to adjust quantity. However, the Buyer no longer has visibility into the Demand Fulfilment available quantity. Provide a single page to view original quantity requested, available to promise quantity, and have a third field to input a new order quantity.

[1152] When the desired quantity is not available, suggest substitute products or alternate suppliers based retailer's substitution rules.

[1153] 6. Pre-Conditions

[1154] 6.1 Shopping cart has items

[1155] 6.2 Supplier updates stock/available to promise data

[1156] No individual supplier stock allocation rules are maintained in Demand Fulfilment

[1157] 7. Post-Conditions

[1158] 7.1 Customer order is split into multiple supplier purchase orders and transmitted

[1159] 7.2 Order status is updated to Open

[1160] 7.3 Electronic Marketplace Solution sends customer order to BOS

[1161] This includes changes made to original BOS suggested order.

[1162] 7.4 Demand Fulfilment inventory levels are decreased

[1163] 8. Data Requirements

[1164] Data In

[1165] Supplier

[1166] Product number

[1167] Quantity desired

[1168] Data Out

[1169] Supplier

[1170] Product number

[1171] Quantity available

[1172] 9. Interfaces

[1173] Interface to BOS to push back final customer order.

[1174] 10. Assumptions

[1175] Use Case Specification: Retrieve Saved Shopping Cart

[1176] 1. Context Diagrams

[1177] Order Capture Saved Shopping Cart

[1178] Order Capture-HOS Aggregated Order

[1179] Order Capture BOS Suggested Order Single Store

[1180] 2. Use Case Actors

[1181] Category Manager/Store Owner (Buyer)

[1182] Customer Management

[1183] 3. Brief Description

[1184] Buyer retrieves a shopping cart that has been previously saved.

[1185] 4. Flow of Events

[1186] 4.1 Basic Flow

[1187] 4.1.1 Buyer clicks Saved Shopping Cart.

[1188] 4.1.2 Buyer selects specific shopping cart from drop down list.

[1189] 4.2 Alternative Flow(s)

[1190] 4.2.1 No saved shopping cart available

[1191] If the Buyer has not previously saved a shopping cart or imported a BOS suggested order, upon clicking Saved Shopping Cart from the main order menu, the Buyer sees a blank page.

[1192] 4.2.2 Selected wrong shopping cart

[1193] If the Buyer selects the incorrect shopping cart, the Buyer can navigate back to the Saved Shopping Cart pick list via the main menu.

[1194] 5. Special Requirements

[1195] 5.1 Usability

[1196] 5.1.1 Pilot—Release 1

[1197] Shopping cart can be saved with a user-defined name.

[1198] Multiple shopping carts can be saved.

[1199] 5.1.2 Pilot—Release 3

[1200] Indicate (i.e. in a different colour) the products in the shopping cart that are on promotion.

[1201] Provide a button to click on to get further details on the promotional products in the shopping cart.

[1202] Allow deletion of a shopping cart from the user interface.

[1203] Limit the maximum number of saved shopping carts to 15.

[1204] For saved BOS suggested order, highlight in a different colour the products in the shopping cart had their BOS prices overridden.

[1205] Provide a side by side view of the BOS price and the Electronic Marketplace Solution price for the line items were generated via a suggested order.

[1206] Set a default saved cart in user profile. Saved cart would automatically be retrieved upon login.

[1207] 6. Pre-Conditions

[1208] 6.3 A shopping cart has been manually saved or automatically populated based on BOS suggested order

[1209] 6.4 User profile indicates whether store has BOS system or not

[1210] 7. Post-Conditions

[1211] 7.1 Buyer can view shopping cart contents.

[1212] Shopping cart includes product, price, and quantity.

[1213] 7.2 Buyer can continue to search and browse entire catalogue.

[1214] 7.3 Buyer can continue to add items to shopping cart.

[1215] 7.4 Buyer can review promotions.

[1216] User profile defines whether BOS Buyer can review promotions. Some Convenience Organised stores may not be allowed to review promotions.

[1217] 7.5 Buyer can add items from promotions page to shopping cart.

[1218] 8. Data Requirements

[1219] Data In

[1220] Shopping cart name

[1221] Data Out

[1222] Supplier

[1223] Product number

[1224] Product description

[1225] Quantity

[1226] Electronic Marketplace Solution price

[1227] Indicator if product is on promotion

[1228] Highlighted price difference between BOS and Electronic Marketplace Solution

[1229] 9. Interfaces

[1230] None

[1231] Use Case Specification: Import HOS/BOS Generated Order

[1232] 1. Context Diagrams

[1233] Order Capture_HOS Aggregated Order

[1234] Order Capture_BOS Suggested Order Single Store

[1235] 2. Use Case Actors

[1236] Back Office System (BOS)

[1237] Home Office System (HOS)

[1238] Customer Management

[1239] 3. Brief Description

[1240] The suggested order generated by the HOS/BOS is loaded into Customer Management and saved as a shopping cart.

[1241] 4. Flow of Events

[1242] 4.1 Basic Flow

[1243] 4.1.1 Electronic Marketplace Solution receives suggested order from HOS/BOS.

[1244] 4.1.2 Electronic Marketplace Solution validates suggested order products and product numbers against catalogue products and product numbers.

[1245] If there is a discrepancy between BOS and Electronic Marketplace Solution, see alternative flow.

[1246] 4.1.3 Electronic Marketplace Solution validates suggested order prices against Electronic Marketplace Solution prices.

[1247] If there is a discrepancy between BOS and Electronic Marketplace Solution, see alternative flow.

[1248] 4.1.4 Electronic Marketplace Solution formats and saves suggested order as a shopping cart.

[1249] 4.2 Alternative Flow(s)

[1250] 4.2.1 Electronic Marketplace Solution rejects line items on suggested order.

[1251] If there is a discrepancy with line items on the HOS/BOS suggested order and Electronic Marketplace Solution catalogue, Electronic Marketplace Solution generates a flat file of the exception line items. The flat file includes the product number, description, and the reason for failure.

[1252] The correct line items on the suggested order are submitted and the exception line items drop off the suggested order.

[1253] Depending on user profile, Electronic Marketplace Solution determines the necessary action for the exception line items:

[1254] Convenience Independents With Electronic Marketplace Solution Installed BOS—Electronic Marketplace Solution overrides the BOS system with changes

[1255] Convenience Organised—Electronic Marketplace Solution provides the changed items in A flat file and Convenience Organised determines if change needs to be accepted

[1256] Convenience Independents With Independent BOS—If the user profile indicates the CI would like automatic updates to the BOS catalogue, then Electronic Marketplace Solution overrides the BOS system with changes. If the user profile indicates the CI would just like to be notified of the change, Electronic Marketplace Solution provides the changed item in A flat file.

[1257] 4.2.2 Electronic Marketplace Solution overrides HOS/BOS price with Electronic Marketplace Solution price.

[1258] If there is a discrepancy with prices on the HOS/BOS suggested order and Electronic Marketplace Solution prices, Electronic Marketplace Solution overrides the HOS/BOS prices.

[1259] Order Management updates HOS/BOS prices when final order is converted into CO/PO.

[1260] 4.2.3 Electronic Marketplace Solution cannot process order for unknown reason

[1261] Electronic Marketplace Solution Help Desk attempts to resolve problem.

[1262] If Electronic Marketplace Solution Help Desk cannot resolve the problem, Electronic Marketplace Solution contacts the Retailer and jointly resolve.

[1263] Electronic Marketplace Solution may push a flat file containing discrepancies to HOS/BOS.

[1264] 5. Special Requirements

[1265] 5.1 Usability

[1266] 5.1.1 Pilot—Release 1

[1267] Automated transfer of suggested order from HOS/BOS to Electronic Marketplace Solution

[1268] Reject line items that do not match the Electronic Marketplace Solution catalogue and process the line items that do match

[1269] For Electronic Marketplace Solution suppliers, generate a flat file of rejected line items due to product number not found or any other reason.

[1270] Override HOS/BOS prices with Electronic Marketplace Solution prices

[1271] Provide a side by side view of the HOS/BOS price and the Electronic Marketplace Solution price for the line items were generated via a suggested order

[1272] Automatically save suggested order as a shopping cart with a meaningful, descriptive name (name format to be determined later)

[1273] From the main ordering menu, Buyer has ability to select one of potentially many shopping carts

[1274] Electronic Marketplace Solution accepts HOS/BOS orders for all suppliers, including orders for suppliers not on the Electronic Marketplace Solution system. Electronic Marketplace Solution generates a report for all order line items from non-Electronic Marketplace Solution suppliers. Orders for non-Electronic Marketplace Solution suppliers are manually placed by the Electronic Marketplace Solution organisation.

[1275] 5.1.2 Pilot—Release 3

[1276] When products change in the Electronic Marketplace Solution catalogue or there is a discrepancy between products in the Electronic Marketplace Solution catalogue and HOS/BOS catalogue (as determined by exception processing when importing the suggested order), CM generates a flat file of all product changes. Depending on user profile, Electronic Marketplace Solution pushes out the changes to BOS, or sends a file of the changes. If the Buyer is sent a file of the changes, the Buyer determines whether to implement changes in BOS/HOS. The goal is to keep the HOS/BOS and Electronic Marketplace Solution catalogues synchronized.

[1277] Alert the Buyer upon login when a suggested order/saved shopping cart exists in Electronic Marketplace Solution. Buyer is able to see saved shopping cart upon navigating to Saved Shopping Cart pick list.

[1278] Send HOS/BOS order straight through to OMS without user intervention user profile indicated HOS/BOS information and ordering preference.

[1279] 6. Pre-Conditions

[1280] 6.1 Retailer user profile indicates whether retailer uses HOS/BOS or not (and interface is developed accordingly)

[1281] 6.2 HOS/BOS generates a suggested order and the Category Manager reviews suggested order in HOS/BOS

[1282] 6.3 HOS/BOS generates order in a format that can be imported by Electronic Marketplace Solution

[1283] 6.4 Translation table between HOS/BOS product numbers and Electronic Marketplace Solution product numbers exists

[1284] 7. Post-Conditions

[1285] 7.1 Validated data has been loaded into Electronic Marketplace Solution and saved in shopping cart format

[1286] 7.2 Electronic Marketplace Solution has sent notification of failed import items to HOS/BOS

[1287] 7.3 Status of order is null—order status becomes Open when Buyer clicks Checkout

[1288] 8. Data Requirements

[1289] Data In

[1290] Supplier

[1291] Product number

[1292] Product description

[1293] Quantity

[1294] BOS price (Retailer's nett price)

[1295] Data Out

[1296] Supplier

[1297] Product number

[1298] Product description

[1299] Quantity

[1300] Flag for failure of BOS import

[1301] Reason codes for failure of BOS import

[1302] 9. Interfaces

[1303] There is a two-way interface between Electronic Marketplace Solution and HOS/BOS.

[1304] 1. The HOS/BOS suggested order file is automatically exported to Electronic Marketplace Solution at the completion of an order in HOS/BOS. This export occurs real-time (is not batched).

[1305] 2. Depending on user profile, the rejected line items due to product number discrepancy are automatically corrected in BOS. If not automatically corrected, the flat file is transmitted to HOS/BOS for manual review.

[1306] 3. The rejected order due to unknown reasons may need to be sent back to HOS/BOS depending if the Electronic Marketplace Solution Help Desk can resolve the issue.

[1307] 10. Assumptions

[1308] 1. HOS/BOS sends Electronic Marketplace Solution the orders for suppliers not supported by Electronic Marketplace Solution. Orders for non-Electronic Marketplace Solution suppliers are manually processed by Electronic Marketplace Solution organisation. (See also Special Requirements)

[1309] Use Case Specification: Update Inventory Levels

[1310] 1. Use Case Diagrams

[1311] Available to Promise

[1312] 2. Use Case Actors

[1313] Supplier's ERP

[1314] Demand Fulfilment

[1315] 3. Brief Description

[1316] Update product inventory levels in Demand Fulfilment.

[1317] 4. Flow of Events

[1318] 4.1 Basic Flow

[1319] 4.1.1 Supplier sends a file containing stock information.

[1320] File is in a predefined Electronic Marketplace Solution format, containing product number and quantity for each available SKU, for each available stock location.

[1321] 4.1.2 Electronic Marketplace Solution loads data.

[1322] 4.1.3 Electronic Marketplace Solution validates data.

[1323] 4.2 Alternative Flow(s)

[1324] 4.2.1 Supplier's file is not sent

[1325] If the supplier's allocations are not received during the scheduled batch time, Electronic Marketplace Solution generates and sends notification to the supplier explaining allocations were not received and product availability in the Electronic Marketplace Solution may be incorrect

[1326] Stock allocations in Demand Fulfilment do not get updated.

[1327] 4.2.2 Supplier's data does not match Electronic Marketplace Solution data

[1328] If there is a discrepancy between the supplier's data and the Electronic Marketplace Solution data, Electronic Marketplace Solution generates a flat file of the discrepancy line items. The flat file includes the product number, quantity, stock location, and reason code for failure.

[1329] The validated products are automatically updated in Demand Fulfilment and the exception products are rejected.

[1330] Electronic Marketplace Solution sends the flat file to the supplier.

[1331] 4.2.3 Supplier submits spreadsheet containing stock allocation data

[1332] If a supplier does not have an ERP, the supplier can submit stock information in a Microsoft Excel spreadsheet.

[1333] The Electronic Marketplace Solution System Administrator loads the spreadsheet data.

[1334] 5. Special Requirements

[1335] 5.1 Usability

[1336] 5.1.1 Pilot—Release 1

[1337] Allocations are updated via an automated, batch process

[1338] Supplier's user profile indicates whether the Demand Fulfilment is a reflection of stock allocation or actual inventory levels from the supplier's ERP

[1339] Supplier is allowed to submit stock allocation data via a spreadsheet format

[1340] 5.1.2 Pilot—Release 3

[1341] 6. Pre-Conditions

[1342] 6.5 Supplier's products and stock locations have been loaded at least once into catalogue

[1343] 7. Post-Conditions

[1344] 7.5 Updated inventory levels

[1345] 8. Data Requirements

[1346] Data In

[1347] Supplier

[1348] Location

[1349] Product number

[1350] Quantity available

[1351] Data Out

[1352] Supplier

[1353] Product number

[1354] Location

[1355] Quantity available

[1356] Notification of non-receipt

[1357] Flat file of discrepancy products

[1358] 9. Interfaces

[1359] Batch interface between Demand Fulfilment and Supplier's ERP.

[1360] 11. Delta

[1361] None

[1362] 12. Assumptions

[1363] The supplier's stock allocation quantity in Demand Fulfilment reflects any transactions that have occurred in Electronic Marketplace Solution since the supplier's ERP was last refreshed.

[1364] Use Case Specification: Review Shopping List

[1365] 1. Context Diagrams

[1366] Order Capture_Top Up Order (Non BOS)

[1367] Order Capture_Saved Shopping Cart

[1368] Order Capture_HOS Aggregated Order

[1369] Order Capture_BOS Suggested Order Single Store

[1370] 2. Use Case Actors

[1371] Store Owner (Buyer)

[1372] Customer Management

[1373] 3. Brief Description

[1374] Buyer reviews the shopping list and selects items for the shopping cart.

[1375] 4. Flow of Events

[1376] 4.1 Basic Flow

[1377] 4.1.1 Buyer retrieves saved shopping cart.

[1378] If desired—otherwise buyer can start a new cart.

[1379] 4.1.2 Buyer clicks Shopping List.

[1380] 4.1.3 Buyer browses Shopping List.

[1381] 4.1.4 Buyer selects products from Shopping List by clicking in the Select check box.

[1382] 4.1.5 Buyer clicks Add to Shopping Cart button.

[1383] 4.1.6 Buyer is brought to Shopping Cart page.

[1384] 4.2 Alternative Flow(s)

[1385] 4.2.1 No shopping list available

[1386] If the Buyer has not previously set up a shopping list, upon clicking “Shopping List” from the main order menu, the Buyer sees a blank page.

[1387] 4.2.2 Buyer cannot find product on shopping list

[1388] If the Buyer cannot find the desired product on the shopping list, provide the ability to search the Store/Company list (otherwise known as Main Catalogue).

[1389] 5. Special Requirements

[1390] 5.1 Usability

[1391] 5.1.1 Pilot—Release 1

[1392] Products can be added to and deleted from the Shopping List.

[1393] Provide functionality to input quantity at the time user is reviewing the shopping list and before the user has added to shopping cart.

[1394] 5.1.2 Pilot—Release 3

[1395] Indicate (i.e. in a different colour) the products in the shopping cart that are on promotion.

[1396] Provide a button to click on to get further details on the promotional products in the shopping cart.

[1397] Provide a Select All button to select all items in Shopping List.

[1398] Provide ability to manually deselect items that are not desired after “Select All” button has been clicked.

[1399] 6. Pre-Conditions

[1400] 6.6 Shopping list is saved.

[1401] Shopping List is manually created via drag and drop functionality or via a file uploaded into the database.

[1402] 6.7 Saved shopping cart is opened.

[1403] If Buyer wants to add items from Shopping List to saved shopping cart, the saved shopping cart must be opened prior to selecting the Shopping List.

[1404] 6.8 User profile/assigned role indicates whether store generates orders in BOS or Electronic Marketplace Solution.

[1405] If store wishes to generate completed POs in BOS, the only saved shopping cart available is an imported suggested order.

[1406] 7. Post-Conditions

[1407] 7.5 Buyer can view shopping cart contents.

[1408] Shopping cart includes product, price, and quantity.

[1409] 7.6 Buyer can continue to search and browse.

[1410] 7.7 Buyer can continue to add items to shopping cart.

[1411] 8. Data Requirements

[1412] Data In

[1413] Shopping list

[1414] Data Out

[1415] Supplier

[1416] Product number

[1417] Product description

[1418] Quantity

[1419] Electronic Marketplace Solution price

[1420] Indicator if product is on promotion

[1421] 9. Interfaces

[1422] None

[1423] 10. Assumptions

[1424] Use Case Specification: Add to Shopping Cart

[1425] 1. Context Diagrams

[1426] Order Capture—Quick Order (Non BOS)

[1427] Order Capture—Saved Shopping Cart

[1428] Order Capture—BOS Suggested Order—Convenience Independent

[1429] Order Capture—BOS Suggested Order—Convenience Organised

[1430] 2. Use Case Actors

[1431] Category Manager/Store Owner (Buyer)

[1432] Customer Management

[1433] 3. Brief Description

[1434] Buyer adds/edits/deletes items and adjusts quantities within shopping cart. Upon checkout the shopping cart is sent to available to promise (ATP).

[1435] 4. Flow of Events

[1436] 4.1 Basic Flow

[1437] 4.1.1 Buyer adds/edits/deletes items to shopping cart.

[1438] 4.1.2 Buyer adjusts quantities.

[1439] 4.1.3 Buyer accepts shopping cart contents and quantities and clicks Checkout.

[1440] 4.1.4 Buyer reviews order total as it is incremented.

[1441] 4.1.5 Customer order is sent to Demand Fulfilment.

[1442] 4.2 Alternate Flow

[1443] 4.2.1 Save shopping cart

[1444] Provide the ability for the Buyer to save the products and quantities as a shopping cart to be retrieved later.

[1445] Buyer clicks on Save Shopping Cart button.

[1446] Buyer enters name of shopping cart.

[1447] Buyer clicks on Save.

[1448] Shopping cart is saved.

[1449] If Buyer wishes to Checkout the shopping cart that was just saved, Buyer navigates to Saved Shopping Cart, selects the shopping cart from the pick list, and clicks Checkout.

[1450] 4.2.2 Cancel customer order

[1451] Provide the ability for the Buyer to exit from the customer ordering process.

[1452] 4.2.3 Buyer continues shopping before checkout

[1453] Buyer clicks on Continue Shopping.

[1454] Buyer can search and browse for more products and add to same shopping cart.

[1455] 5. Special Requirements

[1456] 5.1 Usability

[1457] 5.1.1 Pilot—Release 1

[1458] Standard add/edit/delete shopping cart functionality

[1459] Ability to update quantity

[1460] Ability to remove products from shopping cart Recognize when minimum order quantity is not input and provide a message that informs the Buyer a correction is required.

[1461] Calculate line item order value (quantity multiplied by unit price)

[1462] Calculate total customer order value (sum of line item order value)

[1463] Provide button to Check Out and send shopping cart to Available to Promise

[1464] Provide button to Save Shopping Cart

[1465] Prompt Buyer to input name of shopping cart

[1466] Ability to save multiple shopping carts

[1467] Provide button to Continue Shopping

[1468] Save shopping cart if user session times out.

[1469] 5.1.2 Pilot—Release 3

[1470] Upon clicking “Check out” provide a prompt “Do you want to save this shopping cart?”

[1471] 6. Pre-Conditions

[1472] 6.1 Catalogue is established

[1473] 6.2 Retailer specific pricing is established

[1474] 6.3 Promotion products exist in catalogue

[1475] 6.4 Products have been selected for addition to shopping cart.

[1476] Products can originate from the Shopping List of Store/Company List.

[1477] 7. Post-Conditions

[1478] 7.1 Customer order transmitted to Demand Fulfilment

[1479] 7.2 Shopping cart is emptied; all items are on the customer order

[1480] If the shopping cart has not been saved, the shopping cart is emptied

[1481] 8. Data Requirements

[1482] Data In

[1483] Supplier

[1484] Product number

[1485] Product description

[1486] Quantity

[1487] Electronic Marketplace Solution price

[1488] Indicator if product is on promotion

[1489] Highlighted price difference between BOS and Electronic Marketplace Solution

[1490] Data Out

[1491] Supplier

[1492] Product number

[1493] Quantity

[1494] Electronic Marketplace Solution price

[1495] Total line item dollar value

[1496] Total purchase order dollar value

[1497] Total customer order dollar value

[1498] 9. Interfaces

[1499] None

[1500] 10. Assumptions

[1501] Case Specification Messaging

[1502] 1. Use Case Diagrams

[1503] Community

[1504] 2. Use Case Actors

[1505] User (General)

[1506] Platform

[1507] 3. Brief Description

[1508] Messaging is used within the Electronic Marketplace Solution system for communication between all participants (suppliers, retailers, service providers, Electronic Marketplace Solution, etc.)

[1509] 4. Flow of Events

[1510] 4.1 Basic Flow

[1511] 4.1.1 Email Messages—Electronic Marketplace Solution facilitated

[1512] Electronic Marketplace Solution receives email content (i.e. advertisements, product recalls, special offers, targeted information, etc.) from suppliers, service providers, logistics providers, etc.

[1513] Electronic Marketplace Solution also receives distribution parameters (e.g. target audience) from email content submitter. For certain messages, the audience could be all Electronic Marketplace Solution users.

[1514] A Electronic Marketplace Solution Content Administrator data mines the user profile to obtain the correct distribution list. Depending on the granularity of the target audience request, this could be a simple or complex task

[1515] The email is distributed to the distribution list

[1516] Electronic Marketplace Solution can also develop and distribute Electronic Marketplace Solution specific email

[1517] 4.1.2 Email Messages—User facilitated

[1518] Electronic Marketplace Solution users have the ability to directly (i.e. without Electronic Marketplace Solution Admin intervention) receive, compose, forward, reply to, and delete private emails. This includes emailing fellow Electronic Marketplace Solution users in addition to other Internet contacts.

[1519] A Electronic Marketplace Solution Company can utilize Electronic Marketplace Solution's email functionality to manage and distribute intra-company messages

[1520] 4.1.3 Alert Messages

[1521] Upon logging in to Electronic Marketplace Solution, users can view applicable alerts

[1522] Examples include order status changes, system outages, new messages, new promotions, etc.

[1523] To access the content behind the alert, the user must navigate to the appropriate page (i.e. Promotions) or click on a hyperlink attached to the alert

[1524] 5. Special Requirements

[1525] 5.1 Release 1

[1526] Acquire 3^(rd) party software or ISP provided email to address this functionality

[1527] All Electronic Marketplace Solution generated distribution lists are proprietary information. Emails should be sent in such a manner that the recipients cannot see who else received the message

[1528] All users will have a Electronic Marketplace Solution specific email address (e.g. User3785@Electronic Marketplace Solution.com)

[1529] Manual data query to develop distribution lists based on email addresses in user profiles

[1530] Electronic Marketplace Solution needs the ability to monitor and limit the # of bulk mail emails that are sent out daily. Need an internal business process discussion.

[1531] Users need the ability to compose, read, save, forward, delete, reply to, etc. emails

[1532] Users need the ability to manage emails via folders, create new message folders, move files to and from folders, and delete folders

[1533] Electronic Marketplace Solution needs the ability to send messages to all Electronic Marketplace Solution users

[1534] Ability to send promotional plans (text and attachments only) via messaging.

[1535] Ability to build and manage distribution lists

[1536] Pre-configured folders (i.e. supplier emails are automatically sent to a supplier folder)

[1537] 5.2 Release 3

[1538] Forms can be converted to messages and sent to suppliers, users, or distribution lists

[1539] Automated link between the user profile and the email distribution list/Address book

[1540] 6. Pre-Conditions

[1541] 6.9 User has a Electronic Marketplace Solution account

[1542] 7. Post-Conditions

[1543] 7.6 User can send, receive, view, and manage messages

[1544] 8. Data Requirements

[1545] User profile email address

[1546] 9. Interfaces

[1547] External email software or ISP provided email

[1548] Use Case Specification: Create-Import Content

[1549] 1. Use Case Diagrams

[1550] Community

[1551] 2. Use Case Actors

[1552] Electronic Marketplace Solution Content Management

[1553] Platform

[1554] 3. Brief Description

[1555] Adding content to Electronic Marketplace Solution website. Content includes images, advertising, hot topics, news/current events, career center information, supplier hyperlinks, and Electronic Marketplace Solution notifications and announcements.

[1556] 4. Flow of Events

[1557] 4.2 Basic Flow

[1558] 4.2.1 Pull external content (e.g. news/current events, advertisements, hyperlinks, hot topics, and career center)

[1559] Contact information provider

[1560] Discuss appropriate content, timing, format, and recommended viewers

[1561] Discuss costs of displaying content

[1562] Provider submits content and defines effective dates, desired viewers, and special requirements

[1563] Electronic Marketplace Solution reviews content and provides feedback, as necessary

[1564] 4.2.2 Develop internal content (e.g. Electronic Marketplace Solution announcements, hyperlinks, and hot topics)

[1565] Develop the content

[1566] Determine the audience

[1567] 4.2.3 Add content to template

[1568] Open the template

[1569] Choose the container (i.e. location on page)

[1570] Load content to container

[1571] Define system variables (e.g. effective date and time)

[1572] 4.1.4 Define audience based upon user profile

[1573] Determine groups and/or roles for content

[1574] Tie content to groups and/or roles

[1575] Save

[1576] 4.1.5 Ongoing maintenance

[1577] Monitor available page “real estate”

[1578] Ensure adequate cross-section of material

[1579] Purge obsolete content on a regular basis

[1580] Maintain Groups and Roles as they related to content

[1581] Develop “filler” material for empty containers

[1582] Ensure consistent look and feel

[1583] Testing new content

[1584] 4.2 Alternative Flow(s)

[1585] 4.2.1 Define audience based upon user profile atributes

[1586] In the event Groups or Roles cannot identify the targeted users, querying the user profile database can identify the users.

[1587] Once the users are identified, determine if a new group or role needs to be added to easily manage the association to the content.

[1588] If so, add a group or role and tie content to that group or role

[1589] If not, tie user to content

[1590] 5. Special Requirements

[1591] 5.1 Release 1

[1592] Effective dates (start and end dates) for content display

[1593] Rolling banners

[1594] Content includes images, text, hyperlinks, content (hot topics, career centre, news/current events, etc.), advertisements, etc.

[1595] Content can share page location (i.e. container) and effective dates if targeted users are different

[1596] Content can be target to users based upon BAT's current customer hierarchy fitted to's profile structure

[1597] 5.2 Release 3

[1598] New suppliers can request a limited # (proposed 5) of attributes to gather about Electronic Marketplace Solution users. This information can be used to target content.

[1599] Number of Groups and Roles added to accommodate this should be monitored to prevent excessive maintenance requirements

[1600] 6. Pre-Conditions

[1601] 6.10 Content is developed and ready for import to Electronic Marketplace Solution

[1602] 6.11 Templates have been created

[1603] 6.12 User profiles established

[1604] 6.13 External content providers have been identified and submit content on a regular basis in a predefined format

[1605] 6.14 Standards for content (e.g. size requirements, file formats) have been determined and communicated

[1606] 7. Post-Conditions

[1607] 7.7 Content tied to user profile and page location

[1608] 8. Data Requirements

[1609] Groups

[1610] Roles

[1611] Users

[1612] User profile attributes

[1613] Content

[1614] Effective dates

[1615] User Target information

[1616] 9. Interfaces

[1617] If content is external, it is provided in a format that is easily imported

[1618] Hyperlinks to external sites

[1619] Use Case Specification: Access Content

[1620] 1. Use Case Diagrams

[1621] Community

[1622] 2. Use Case Actors

[1623] User (General)

[1624] Platform

[1625] 3. Brief Description

[1626] Method in which user can access content (based upon user profile) available on the Electronic Marketplace Solution website

[1627] 4. Flow of Events

[1628] 4.3 Basic Flow

[1629] 4.1.1 User enters the Electronic Marketplace Solution and can view content

[1630] The user logs into Electronic Marketplace Solution

[1631] The user profile is activated (e.g. user specific content is pulled, security access is activated, etc.)

[1632] User can view their default page

[1633] Advertisements, logos, other images, Electronic Marketplace Solution messages, and hyperlinks are automatically displayed based upon requirements and user profile

[1634] User can navigate to other content areas (Hot Topics, News/Current Events, Career Center, and Messaging)

[1635] The content displayed on the other content areas is also based upon the user profile designations (i.e. Group, Role, User, etc.)

[1636] Chat rooms and discussion groups will be driven by the user. Should be monitored and managed (i.e. security access) by Electronic Marketplace Solution. Access could be limited by Groups and Roles. A 3^(rd) party software is recommended.

[1637] 5. Special Requirements

[1638] 5.1 Release 1

[1639] Easy to navigate

[1640] 3^(rd) Party software, integrated with user profile, to provide discussion group and chat room functionality. The access to these functionalities can be turned on or off based upon user profile/security access.

[1641] Community content housed on separate tabs or pages to avoid information overload

[1642] 5.2 Release 3

[1643] User can personalize (similar to Yahoo! and Excite functionality) the display of certain content areas (e.g. News/Current Events, Hot Topics, etc.)

[1644] 6. Pre-Conditions

[1645] 6.15 User has account with Electronic Marketplace Solution

[1646] 6.16 User profile has been established

[1647] 6.17 Content has been created, imported, and associated to user profiles

[1648] 7. Post-Conditions

[1649] 7.8 User can view targeted content

[1650] 8. Data Requirements

[1651] User profile

[1652] Community content

[1653] 9. Interfaces

[1654] Discussion Group/Chat Room provider

[1655] Use Case Specification: Query Order Status

[1656] 1. Use Case Diagrams

[1657] Order Tracking

[1658] 2. Use Case Actors

[1659] Category Manager/Store Owner (Buyer)

[1660] Customer Management

[1661] 3. Brief Description

[1662] Buyer views order status.

[1663] 4. Flow of Events

[1664] 4.1 Release 1

[1665]4.1.1 Basic Flow

[1666] Query Using Order Summary

[1667] Buyer navigates to Order tab in Customer Management

[1668] Buyer selects Order Summary

[1669] Buyer views all purchase orders with a status not equal to Closed

[1670] 4.1.2 Alternative Flow(s)

[1671] Query Using Order Search

[1672] Buyer navigates to Order tab in Customer Management

[1673] Buyer selects Order Search

[1674] Buyer inputs purchase order number and/or Buyer selects status from drop down box

[1675] Buyer clicks Search

[1676] Search results are populated in lower pane

[1677] Query Using Order Status

[1678] Buyer navigates to Order tab in Customer Management

[1679] Buyer selects an order status of Unconfirmed, Accepted, Accepted With Changes, Shipped, Paid, or Closed from the menu

[1680] Buyer inputs purchase order number (if desired)

[1681] Buyer clicks Search

[1682] Search results are populated in lower pane

[1683] 4.2 Release 3

[1684] 4.2.1 Basic Flow

[1685] Buyer goes to Customer Order Summary in Order Management System

[1686] Buyer drills down via hyperlink to specific Customer Order

[1687] Buyer drills down via hyperlink to specific Purchase Order within Customer Order

[1688] Buyer drills down via hyperlink to specific line items within Purchase Order

[1689] Buyer views line item status

[1690] 4.2.2 Alternative Flow(s)

[1691] Buyer begins drill down by Customer Order number in Order Management System

[1692] Buyer begins drill down by Supplier in Order Management System

[1693] Buyer begins drill down by Product in Order Management System

[1694] 5. Special Requirements

[1695] 5.1 Release 1

[1696] 5.1.1 Provide an Order Status Summary hyperlink on main Order menu

[1697] Upon clicking, the user is presented with all Orders that do not have a status of Closed. Orders are sorted in descending date.

[1698] 5.1.2 Provide Status hyperlinks on main Order menu

[1699] Hyperlinks for Unconfirmed, Accepted, Accepted With Changes, Shipped, Paid, Closed

[1700] 5.1.2 Provide Order Search functionality

[1701] Search on Purchase Order Number or Status

[1702] 5.2 Release 3

[1703] 5.2.1 Retailer can view a Retailer Status Summary Page (see Update Order Use Case)

[1704] 5.2.2 Modify order

[1705] Upon querying order, Buyer has the ability to modify line items on the order (see Modify Order Use Case)

[1706] 6. Pre-Conditions

[1707] 6.18 Buyer is logged into Electronic Marketplace Solution and selected to go to Customer Management

[1708] 6.19 At least one purchase order is created

[1709] 7. Post-Conditions

[1710] 7.9 Buyer is aware of order status and details

[1711] 8. Data Requirements

[1712] Customer Order Information (Release 3)

[1713] Purchase Order Information

[1714] Supplier Sales Order Information

[1715] Status Information

[1716] 9. Interfaces

[1717] All external interface requirements have been captured in the Update Order Use Case

[1718] Use Case Specification: Update Order

[1719] 1. Use Case Diagrams

[1720] Order Tracking

[1721] 2. Use Case Actors

[1722] Supplier's ERP

[1723] Demand Fulfilment

[1724] Customer Management

[1725] BOS

[1726] 3. Brief Description

[1727] Update customer/purchase order data (i.e., status, unit price, delivery date, etc.).

[1728] 4. Flow of Events

[1729] 4.1 Basic Flow

[1730] 4.1.1 Receive Updated Data from Within Electronic Marketplace Solution

[1731] Buyer clicks Accept in CM upon reviewing ATP data from DF

[1732] Electronic Marketplace Solution automatically updates status of PO to Unconfirmed

[1733] Buyer views PO in Order Summary Page

[1734] 4.1.2 Receive Updated Order Data from Supplier ERP

[1735] Purchase Order is sent to Supplier

[1736] Supplier processes purchase order and converts to sales order

[1737] Supplier generates sales order flat file with updated PO Number, Delivery Date, Quantity, Price, etc.

[1738] Batch process imports sales order flat file into Electronic Marketplace Solution

[1739] Electronic Marketplace Solution automatically updates status to Accepted, Accepted With Changes, Shipped, Closed etc.

[1740] If status is anything other than Unconfirmed or Accepted, Electronic Marketplace Solution generates a PO Note with details.

[1741] Buyer views PO in Order Summary Page

[1742] 4.1.3 Receive Updated Receipt Data from BOS

[1743] Goods are receipted in BOS

[1744] BOS generates a flat file containing the PO Number, Product Number, and Quantity Received

[1745] Batch process imports BOS file into Electronic Marketplace Solution

[1746] Electronic Marketplace Solution automatically updates status to Received

[1747] Buyer views PO in Order Summary Page

[1748] 4.1.4 Receive Updated Payment Data from Payment Software Solution

[1749] Buyer triggers payment

[1750] Payment Software Solution generates a flat file containing the PO Number and notification of payment

[1751] Batch process imports payment flat file into Electronic Marketplace Solution

[1752] Electronic Marketplace Solution automatically updates status to Paid

[1753] Buyer views PO in Order Summary Page

[1754] 4.1.5 Receive Updated Payment Data from Supplier

[1755] Supplier received payment

[1756] Supplier generates flat file with PO Number and notification of payment received

[1757] Batch process imports payment flat file into Electronic Marketplace Solution

[1758] Electronic Marketplace Solution automatically updates status to Closed

[1759] Buyer views PO in Order Summary Page

[1760] 4.2 Status Definitions and Triggers

[1761] 4.2.1 Release 1

[1762] As an order proceeds through its life cycle from order capture to payment, a status code for each line on the order will be kept in Electronic Marketplace Solution. The table below describes the statuses available and who triggers the status. Most of the statuses are updated automatically, and will be limited to 10 characters on the user interface and are abbreviated as follows: Status Abbreviation Definition Who Triggers Basic Flow Un- Uncomfirmd Customer Order is split Buyer triggers confirmed into multiple purchase by clicking orders Accept in CM. Accepted Accepted Sales Order received by Supplier Electronic Marketplace triggers by Solution and there are no sending batch changes from initial file from ERP. customer order Accepted AccWith Sales Order received by Supplier With Chg Electronic Marketplace triggers by Changes Solution with changes sending batch from initial customer order file from ERP. Invoiced Invoiced Goods are shipped and Supplier invoice is generated and triggers by sent. sending batch file from ERP. Received Received Products received into Buyer retailer's inventory system triggers by (BOS) receipting goods in BOS. BOS sends a batch file to Electronic Marketplace Solution. Closed Closed Payment is received and Supplier accepted by Supplier triggers by sending batch file from ERP. Alternate Flow Supplier SuppCancel Supplier can not fulfil Supplier Cancelled predefined order terms

[1763] 4.2.2 Release 3

[1764] With the implementation of Order Management System, additional statuses will be valid: Status Definition Who Triggers Basic Flow Un- Customer Order is split into multiple Buyer confirmed purchase orders triggers by clicking Accept in CM. Accepted Sales Order received by Electronic Supplier Marketplace Solution and there are no triggers by changes from initial customer order sending batch file from ERP. Accepted Sales Order received by Electronic Supplier With Marketplace Solution with changes triggers by Changes from initial customer order sending batch file from ERP. Shipped Goods are shipped. This status is Supplier only used if the invoice is not triggers by generated at the time the goods are sending batch shipped. If the invoice is generated at file from ERP. the time the goods are shipped, the order goes directly from a status of Accepted to a status of Invoiced. Invoiced Goods are shipped and invoice is Supplier triggers by generated and sent. sending batch file from ERP. Received Products received into retailer's Buyer triggers by inventory system (BOS) receipting goods in BOS. BOS sends a batch file to Electronic Marketplace Solution. Paid Retailer has initiated payment for Buyer triggers by invoiced goods. initiating payment in Electronic Marketplace Solution. Closed Payment is received and accepted by Supplier triggers by Supplier sending batch file from ERP. Alternate Flow Partially Goods have been partially shipped Supplier Shipped Partially Received partial goods due to partial Buyer Received goods delivered or damaged goods upon delivery Supplier Supplier can not fulfil predefined Supplier Cancelled order terms Customer Customer does not agree with sales Buyer Cancelled order Customer Manually triggered Buyer Cancel- lation Request Supplier Manually triggered Supplier Cancel- lation Request Customer Manually triggered Buyer Change Order Request

[1765] 4.3 Valid Status Changes

[1766] 4.3.1 Release 1

[1767] With Release 1, status changes occur based on the triggers in the above table. A status change can occur from any one status to another; there is no intelligence built into the system that restricts movement from one status to another.

[1768] 4.3.2 Release 3

[1769] With Release 3, there are restrictions around movement from one status to another. Business rules based on the below table determine valid status changes. Order Status TO Ac- cept- Cus- Sup- ed Sup- Cus- tomer plier Un- Ac- With Partially Partially plier tomer Can- Can- Cus- con- cept- Chang- Re- In- Partially Re- In- Can- Can- cel- cel- tomer FROM firmed ed es Shipped ceived voiced Paid Closed Shipped ceived voiced celled celled lation lation Change Un- X X X X X X con- firmed Accept- X X X X X X X X X ed Accept- X X X X ed With Chang- es Shipped X X X Re- X X X ceived In- X X X X X voiced Paid X Closed Partially X X X X X X Shipped Partially X X X X X Re- ceived Partially X X X X X X In- voiced Supplier Cancelled Customer Cancelled Customer X Cancel- lation Request Supplier X Cancel- lation Request Customer X X X X X Change Order Request

[1770] 5. Special Requirements

[1771] 5.1 Release 1

[1772] Provide an Order Status Summary page showing order details in a single page view. The summary is a static page with no hyperlinks to drill down into further detail. The summary page contains the original purchase order data. Confirmed Delivery PO Date Order Status Date PO Note PO #1228 10-Aug-00 Unconfirmed 15-Aug-00 PO #1023  9-Aug-00 Accepted With 15-Aug-00 PO Note Changes PO  6-Aug-00 Shipped 12-Aug-00 PO Note #945 PO #902  2-Aug-00 Paid  5-Aug-00

[1773] Any modifications to the original purchase order (changes to quantity, price, etc.) are viewed in a PO Note from the Order Status Summary Page. The user clicks on the PO Note, which provides a running history about changes made to the PO Order. Changes can includes:

[1774] Supplier changes quantity based on availability (if supplier is out of stock quantity is set to zero)

[1775] Supplier changes price

[1776] The Supplier cannot automatically delete a line item of substitute an alternate product for a line item on the PO. If the line item is not available, quantity is set to zero. If the Buyer wants an alternate product, a new PO must be created.

[1777] Supplier confirmed delivery date is automatically updated on the CM user interface.

[1778] All changes made to a BOS generated order are communicated back to BOS.

[1779] Any purchase orders that have been changed by the supplier will be given the status “Accepted with Changes”.

[1780] An e-mail notification is generated alerting the Buyer that a purchase order exists with status Accepted With Changes. The alert contains the PO Number and a summary of the changes as detailed in the PO Note.

[1781] An e-mail notification is generated alerting the Buyer that a purchase order is in dispute (status of Customer Change Order Request or Customer Cancellation Request). The alert contains the PO Number and a summary of the dispute as detailed in the PO Note.

[1782] 5.2 Release 3

[1783] Order Status Summary page has more detail. Ability to drill down (hyperlink) from a Customer Order status summary page to PO detail and order line detail. See example below: Supplier Confirmed ID/ Order Delivery Payment Amount Buyer Name Date Name Status Date Status Outstanding Cust. Order #100 6-Aug-00 PO #945 8-Aug-00 BATA Shipped 12-Aug-00 Unconfirmed PO #144 8-Aug-00 COKE Received 10-Aug-00 Paid PO #858 9-Aug-00 Davids Confirmed 21-Aug-00 Closed Cust. Order #101 7-Aug-00 PO #A3R 9-Aug-00 Nestle Accp. PO #222 8-Aug-00 Pepsi w- Cha Cancelled Cust. Order #102 8-Aug-00 — — — — — — — — —

[1784] Provide a side-by-side view on the single page summary of the original purchase order line item data and the Accepted With Changes purchase order line item data.

[1785] Highlight in a different colour the customer order and line items that were altered from original customer order.

[1786] Buyer can capture a partial goods receipt in OMS. For Pilot, goods receipt can only occur in the BOS.

[1787] 6. Pre-Conditions

[1788] 6.20 Customer order is split into one purchase order per supplier and transmitted to the supplier's ERP.

[1789] Not relevant for Pilot—only one supplier.

[1790] 7. Post-Conditions

[1791] 7.10 Supplier sends confirmation of delivery date, updated quantity and price (if applicable).

[1792] Delivery date is automatically updated on the CM user interface. Updated quantity and price are reflected in the PO Note.

[1793] 7.11 Electronic Marketplace Solution sends Accepted and Accepted With Changes purchase order to BOS.

[1794] Includes changes (quantity, price) made to originally generated BOS suggested order.

[1795] 8. Data Requirements and Interfaces

[1796]8.1 Release 1

[1797] With Release 1, interfaces are based on the following systems:

[1798] CM

[1799] Supplier ERP

[1800] BOS Input Output Status Interface(s) Data Inputs Interface(s) Data Outputs Basic Flow Unconfirmed None CM to Purchase Order Supplier Information ERP Purchase Order CM to BOS #'s mapped to Customer Order # Line Item Detail Accepted With Supplier Purchase CM to Buyer Changes manual online Order Supplier cancellation entry Information ERP or or Supplier with changed Supplier In ERP to fields = Supplier Box CM Sales Order Supplier Sales Order # Supplier Sales Order # mapped to Buyer PO # New Quantity New Unit Price New Total Price Estimated Delivery Date Invoiced Supplier NEED TO NEED TO ERP to DETERMINE DETERMINE Electronic Marketplace Solution (Payment Software Solution and CM) Received Buyer Goods manual online Receipt Data entry PO/SO # or reference BOS/POS Customer to Order # Electronic Received Marketplace Quantity Solution Matching exceptions BOS/POS PO adjustments Closed Supplier NEED TO Supplier ERP sends ERP to DETERMINE AR notification to Electronic CM Marketplace Solution Alternative Flow Supplier Supplier Reason Code: Retailer BOS Cancelled ERP or (Credit terms, Supplier Obsolete manual online product, Back entry order is not to accepted, Electronic Delivery Marketplace terms, etc) Solution SO/PO/CO Information

[1801] 8.2 Release 3

[1802] With Release 3, interfaces are based on the following systems:

[1803] OMS

[1804] CM

[1805] Supplier ERP

[1806] BOS Input Output Status Interface(s) Data Inputs Interface(s) Data Outputs Basic Flow Open CM to Customer OMS to Purchase Order OMS Order Supplier Information information ERP Purchase Order Customer OMS to BOS #'s mapped to Order # Customer Order # Supplier Line Item Detail Information Line Item Detail Accepted Supplier Purchase OMS to Buyer With manual online Order Supplier Acceptance Changes entry Information ERP or or Supplier with changed Supplier In ERP to fields = Supplier Box OMS Sales Order Supplier Sales Order # Supplier Sales Order # mapped to Buyer PO # New Quantity New Unit Price New Total Price Estimated Delivery Date Shipped Supplier Advanced ERP or Shipping Notice: Supplier PO/SO/CO manual online Information entry Quantity to shipper per Electronic line item Marketplace Delivery date Solution Shipping method Received Buyer Goods manual online Receipt Data entry PO/SO # or reference BOS/POS Customer to Order # Electronic Received Marketplace Quantity Solution Matching exceptions BOS/POS PO adjustments Invoiced Supplier NEED TO NEED TO ERP to DETERMINE DETERMINE Electronic Marketplace Solution (Payment Software Solution and OMS) Paid Payment NEED TO Payment Software Software DETERMINE Solution to OMS Solution to Electronic Marketplace Solution Closed Supplier NEED TO Supplier ERP sends ERP to DETERMINE AR notification to Electronic OMS Marketplace Solution Alternative Flow Partially Supplier Advanced Shipped ERP or Shipping Notice: Supplier PO/SO/CO manual online Information entry Quantity to shipper per Electronic line item Marketplace Delivery date Solution Shipping method Partially Buyer Goods Received manual online Receipt Data entry PO/SO # or reference BOS/POS Customer to Order # Electronic Received Marketplace Quantity Solution Matching exceptions BOS/POS PO adjustments Partially Supplier NEED TO Supplier ERP sends Invoiced ERP to DETERMINE invoice to Payment Electronic Software Solution Marketplace and OMS Solution (Payment Software Solution and OMS) Supplier Supplier Reason Code: Retailer BOS Cancelled ERP or (Credit terms, Supplier Obsolete manual online product, Back entry order is not to accepted, Electronic Delivery Marketplace terms, etc) Solution SO/PO/CO Information Customer OMS to Retailer BOS Reason: (Price Cancelled Supplier changes, ERP or available Supplier quantity, desired In-Box quantity, Retailer delivery terms, BOS etc) SO/PO/CO information Customer Cancellation Request Supplier Cancellation Request Customer Change Order Request

[1807] Use Case: Submit Claim or Return Request (Phase 1)

[1808] 1. Use Case Diagrams

[1809] Claims and Returns

[1810] 2. Use Case Actors

[1811] Category Manager/Store Owner (Buyer)

[1812] Order Management System

[1813] Customer Management

[1814] 3. Brief Description

[1815] Buyer alerts supplier that product needs to be returned and requests replacement or submits claim.

[1816] 4. Flow of Events

[1817] 4.1 Basic Flow (Release 3)

[1818] 4.1.1 Buyer navigates to Returns/Claim Request Cart.

[1819] 4.1.2 Buyer inputs return information:

[1820] APN or Product Number

[1821] Supplier

[1822] Quantity

[1823] Purchase Order Number (if available)

[1824] Invoice Number (if available)

[1825] Reason Code

[1826] 4.1.3 Buyer selects Replacement or Request Credit.

[1827] 4.1.4 Buyer adds 2^(nd) return line item

[1828] 4.1.5 Buyer clicks “Submit”

[1829] 4.1.5 Electronic Marketplace Solution converts Returns/Claims Cart to an e-mail.

[1830] 4.1.6 E-mail is sent to supplier's customer service representative as defined in supplier user profile.

[1831] 4.1.7 E-mail is populated in Returns/Claims Request History folder

[1832] 4.2 Alternative Flow(s)

[1833] 4.2.2 Buyer can not find product number

[1834] If the Buyer does not know the product number, the Buyer can navigate to the catalogue and search and browse. Upon finding the product number, the Buyer manually writes it down, navigates back to the Returns/Claim Request Cart, and inputs the product number.

[1835] 5. Special Requirements

[1836] 5.1 Usability (release 3)

[1837] Input product using search functionality

[1838] Populate product description upon entering product number

[1839] Select supplier from drop down list. Supplier drop down list is populated with available suppliers for that product (APN #) as defined in buyer user profile.

[1840] Select replacement or credit for each line item on the form

[1841] Select reason codes from drop down list. Reason codes are defined as:

[1842] Damaged

[1843] Over-stocked

[1844] Expired

[1845] Product Recall

[1846] Other

[1847] Ability to enter multiple returns from different suppliers in single cart

[1848] Ability to split line items in cart by supplier and send multiple e-mails to the supplier's customer service departments

[1849] Save submitted Returns/Claims Carts in a history folder to later be retrieved

[1850] Date/time stamp is generated when e-mail is sent. This date/time stamp is used for identification and tracking of claim.

[1851] Order status is updated as a result of claim being processed (status =Pending Claim?)

[1852] Invoice status is updated as a result of claim being processed (status =Pending Claim?)

[1853] 6. Pre-Conditions (Release 3)

[1854] 6.21 Buyer has goods to return

[1855] 7. Post-Conditions (Release 3)

[1856] 7.12 E-mail is sent to supplier

[1857] 7.13 Buyer can view e-mail in Claims History folder

[1858] 7.14 Order/Invoice status is updated

[1859] 8. Data Requirements

[1860] On-line form fields

[1861] Date and Time (automatically generated)

[1862] Product # or APN (manual entry—required field)

[1863] Supplier Drop Down List (generated by mapping user profile defined suppliers to entered APN—required field)

[1864] Replacement or Credit drop down menu (manual entry—required field)

[1865] Quantity (manual entry—required field)

[1866] Reason Code Selection (manual entry—required field)

[1867] Purchase Order # (manual entry—optional field)

[1868] Invoice # (manual entry—optional field)

[1869] Supplier Customer Service Contact email (automatically driven off of supplier profile)

[1870] Buyer contact information—cust. #, contact name/email, etc. (automatically driven off buyer profile)

[1871] All fields transferred in email

[1872] 9. Interfaces

[1873] Mechanism to send supplier email

[1874] 13. Delta—to be revisited as requirements for Release 3

[1875] currently does not offer Returns/Claims functionality and all functionality in this use case needs to be customized. The customisation could potentially leverage the shopping cart concept. Claims and returns are added to a shopping cart, similar to a customer order, and distributed to multiple suppliers upon clicking Accept/Submit. Need to do further research on what module this functionality should reside in, where to store the shopping cart/e-mail for later retrieval, etc.

[1876] Searching on product numbers from the Returns/Claims Cart requires customisation. Ideally the Buyer inputs the customer number and upon tabbing off the field the description of the product is retrieved from the catalogue. This validation would help the Buyer ensure the correct product number was input.

[1877] Populating a drop down list with valid suppliers requires customisation. Valid suppliers for a product would be driven off the Buyer's user profile.

[1878] Use Case Specification: Modify Order in OMS

[1879] 1. Use Case Diagrams

[1880] Order Tracking

[1881] 2. Use Case Actors

[1882] Category Manager/Store Owner (Buyer)

[1883] Order Management System

[1884] 3. Brief Description

[1885] Buyer can modify line items for orders after they have been transmitted to suppliers.

[1886] 4. Flow of Events

[1887] 4.4 Basic Flow

[1888] 4.1.1 Buyer modifies quantity and/or product of an order

[1889] Buyer navigates to Customer Order and uses hyperlinks to drill down to line item on a Purchase Order (Alternate Flow: Buyer searches directly on Purchase Order number)

[1890] Buyer clicks “Modify”

[1891] Buyer has the ability to:

[1892] Update quantity desired

[1893] Delete line item

[1894] Buyer clicks “Save”

[1895] Modified purchase order is sent to supplier's ERP in the next batch run

[1896] 4.1.2 Buyer updates received goods quantity on a Shipped Order or Partially Shipped Order (non BOS)

[1897] Buyer navigates to Customer Order.

[1898] Buyer navigates to Purchase Order.

[1899] Buyer navigates to line item on Purchase Order.

[1900] Buyer clicks “Modify”.

[1901] Buyer has the ability to:

[1902] Update quantity received

[1903] Buyer clicks “Save”

[1904] 4.2 Alternative Flow(s)

[1905] 4.2.3 Buyer decides not to modify order

[1906] Buyer has decided not to adjust the order and leave as is.

[1907] Buyer clicks “Cancel” and is returned to the Purchase Order view.

[1908] 4.2.4 Buyer cancels entire purchase order for a supplier

[1909] Buyer has decided to delete all line items on the purchase order and cancel the entire order.

[1910] Buyer navigates to Customer Order.

[1911] Buyer navigates to Purchase Order.

[1912] Buyer navigates to line item on Purchase Order.

[1913] Buyer clicks “Check All”.

[1914] Buyer clicks “Delete”.

[1915] Buyer clicks “Save”:

[1916] 5. Special Requirements

[1917] 5.1 Release 1

[1918] 5.1.1 Cannot modify an order for Release 1

[1919] OMS will not be implemented for Release 1. Instead, Customer Management will be used to provide order status and tracking functionality. An order cannot be modified in Customer Management.

[1920] 5.2 Release 3

[1921] 5.2.1 Edit box to adjust quantity of product

[1922] 5.2.2 Ability to delete line item

[1923] 5.2.3 Button to save changes

[1924] 5.2.4 Ability for Buyer to cancel by customer order, by purchase order, or by line item

[1925] 5.2.5 Order status defines whether an order can be modified or not.

[1926] e.g. When an order is “Shipped” order can not be changed

[1927] 5.2.6 Edit box to adjust quantity of goods received

[1928] For stores without a POS/BOS, ability to input quantity of goods receipt directly into Electronic Marketplace Solution

[1929] 6. Pre-Conditions

[1930] 6.22 Order exists in OMS (Release 3)

[1931] 7. Post-Conditions

[1932] 7.15 Purchase order is modified (Release 3)

[1933] 7.16 Customer order is updated with new purchase order details (Release 3)

[1934] 7.17 Purchase order is resubmitted to supplier for acceptance (Release 3)

[1935] 7.18 Modified purchase order is pushed back to BOS (Release 3)

[1936] 8. Data Requirements

[1937] Customer Order/Purchase Order/Sales Order information

[1938] Changed Fields

[1939] Supplier change order by date

[1940] 9. Interfaces

[1941] Supplier's ERP. Modified purchase orders are sent to supplier's ERP. This is a batch process.

[1942] BOS. Modified purchase orders are sent back to BOS. This is a batch process.

[1943] Use Case Specification: Pass Payment Confirmation/Order Status Change from eBPP system to Electronic Marketplace Solution

[1944] 1. Context Diagrams

[1945] Context_Invoice and Payment (Electronic Payment and Cash Payment)

[1946] 2. Use Case Actors

[1947] eBPP system

[1948] ELECTRONIC MARKETPLACE SOLUTION

[1949] 3. Brief Description

[1950] Once the bank has processed payments, the bank sends a file to the eBPP system system stating the payment has been processed. The file will contain transaction reference numbers. eBPP system must pass this file to Electronic Marketplace Solution on a real-time basis.

[1951] 4. Flow of Events

[1952] 4.1 Basic Flow

[1953] As is done today, the bank sends a file to each manufacturers' ERP system after payments have been processed to balance their account reconciliation file.

[1954] The manufacturers' ERP system must then send a file to Electronic Marketplace Solution to change the status of the invoice to “Invoice Paid”.

[1955] 4.2 Alternative Flow(s)—TBD based upon discussions with eBPP system.

[1956] 5. Special Requirements—TBD based upon discussions with eBPP system.

[1957] 5.1 Requirement Category (i.e. usability)

[1958] 6. Pre-Conditions

[1959] 6.1 Insert Pre-Condition

[1960] Payments have been successfully executed by the retailer and received by the manufacturer.

[1961] 7. Post-Conditions

[1962] This file transfer from eBPP system to Electronic Marketplace Solution updates order status' on Electronic Marketplace Solution.

[1963] 8. Data Requirements

[1964] This process is the same process as occurs today—the bank processes all transactions and sends a file to the manufacturer's ERP system. The ERP system must then pass the file to Electronic Marketplace Solution.

[1965] 9. Interfaces

[1966] The manufacturers ERP file will contain the payment information. ELECTRONIC MARKETPLACE SOLUTION will change the invoice status from “payment executed” to “Payment complete.”

[1967] Use Case Specification: Payment Confirmation/Order Status Change

[1968] 1. Context Diagrams

[1969] Context_Invoice and Payment (Electronic Payment)

[1970] 2. Use Case Actors

[1971] Bank

[1972] Suppliers' ERP System

[1973] eBPP system

[1974] 3. Brief Description

[1975] Once the bank has processed payments, the bank sends a file to the Suppliers' ERP system stating the payment has been processed. The file will contain transaction reference numbers.

[1976] The bank will also send this file to eBPP system.

[1977] 4. Flow of Events

[1978] 4.1 Basic Flow

[1979] As is done today, the bank sends a file to each manufacturers' ERP system after payments have been processed to balance their account reconciliation file.

[1980] The manufacturers' ERP system must then send a file to change the status of the invoice to “Invoice Paid”.

[1981] The bank will also send the file to eBPP system, which will change the status of the invoice to “invoice paid”.

[1982] 4.2 Alternative Flow(s)—TBD based upon discussions with eBPP system.

[1983] 5. Special Requirements—TBD based upon discussions with eBPP system.

[1984] 5.1 Requirement Category (i.e. usability)

[1985] 6. Pre-Conditions

[1986] 6.1 Insert Pre-Condition

[1987] Payments have been successfully executed by the retailer and received by the manufacturer.

[1988] 7. Post-Conditions

[1989] The file transmittal will result in an invoice order change on eBPP system to “invoice paid.”

[1990] 8. Data Requirements

[1991] This process is the same process as occurs today- the bank processes all transactions and sends a file to the manufacturer's ERP system.

[1992] The bank will also send the file to eBPP system to update the system.

[1993] 9. Interfaces

[1994] Bank file sent to eBPP system. File format TBD per, discussions with and eBPP system.

[1995] Use Case Specification: Send Payment File to Bank

[1996] 1. Context Diagrams

[1997] Context_Invoice and Payment (Electronic Payment)

[1998] 2. Use Case Actors

[1999] eBPP system

[2000] Bank

[2001] 3. Brief Description

[2002] Retailers will execute payments via eBPP system. eBPP system will translate those payments into an AUS BECS/ACH format and transmit the file to the bank for processing. Payments will be transferred to the bank on a real-time basis.

[2003] 4. Flow of Events

[2004] 4.1 Basic Flow

[2005] Retailers will execute payments via eBPP system.

[2006] eBPP system formats the payments to AUS BECS/ACH standards.

[2007] Throughout the day, eBPP system transmits the payment file to the bank.

[2008] 4.2 Alternative Flow(s)—TBD based upon discussions with eBPP system.

[2009] 5. Special Requirements—TBD based upon discussions with eBPP system.

[2010] 5.1 Requirement Category (i.e. usability)

[2011] 6. Pre-Conditions

[2012] 6.1 Insert Pre-Condition

[2013] Retailers execute payments onto eBPP system throughout the day.

[2014] 7. Post-Conditions

[2015] eBPP system will have transmitted all payment instructions to the bank for execution.

[2016] 8. Data Requirements

[2017] eBPP system will transfer the payments to the bank. The file sent to the bank will contain: purchase order number, invoice number, payment confirmation number, retailers bank name, retailers bank routing number, retailers bank account number, manufacturers bank name, manufacturers bank routing number, manufacturers bank account number, and value date of the payment.

[2018] 9. Interfaces

[2019] On a real-time basis throughout the day, eBPP system will gather all payment authorizations, format the information into appropriate AUS BECS/ACH file format standards, and send the file to the bank.

[2020] 1. Context Diagrams

[2021] Context_Invoice and Payment (Electronic Payment)

[2022] 2. Use Case Actors

[2023] Retailer

[2024] eBPP system

[2025] 3. Brief Description

[2026] Once the retailer has reviewed the invoice, they will make a payment via the “Execute Payment” screen.

[2027] 4. Flow of Events

[2028] 4.1 Basic Flow

[2029] Once the retailer has reviewed the invoice, and they decide to make payment.

[2030] The retailer clicks on the “Execute Payment” button.

[2031] The retailer sees a security message-verify with eBPP system.

[2032] The retailer is presented with a screen that lists the invoice number, item, price, quantity and total dollar amount due.

[2033] Fields exist which ask the retailer to input: bank account number, bank routing number, value date of payment, dollar amount. Allows multiple retailer bank accounts. (Confirm w/eBPP system)

[2034] Functionality is required to allow the retailer to enter the manufacturer's bank information once, and then each time they make a payment to that particular retailer, they can access a drop down menu which already contains the detailed bank information. (Confirm w/eBPP system.)

[2035] Functionality is also required for retailers to future date payments. (Confirm w/eBPP system)

[2036] Once all of the information is entered, the retailed pushes the “Submit Payment” button.

[2037] eBPP system will then generate a confirmation number for the retailer, which can be added in an BECS/ACH field to the bank, so that a) the retailer has confirmation of their transaction, and b) the retailer can call the bank with the transaction number for inquiries. This feature would add to the retailer's comfort in submitting online payments. (Confirm w/eBPP system)

[2038] Point to discuss with eBPP system: Detailed BECS/ACH file formats for AUS market. Exactly what field would allow for transaction number to be attached? Need to attach invoice number, and also transaction number directly tied to the payment.

[2039] Once the retailer hits “submit payment”, and they receive their confirmation number, they log out.

[2040] Payments are transmitted between eBPP system and the bank on a real time basis throughout the day. (Confirm w/eBPP system. Could be twice a day batch. If so, how impact transaction reference number allocations?)

[2041] The invoice status is then changed to “Payment Executed” on eBPP system, and eBPP system has a feed back to Electronic Marketplace Solution to update the order status.

[2042] 4.2 Alternative Flow(s)—TBD based upon discussions with eBPP system.

[2043] 5. Special Requirements—TBD based upon discussions with eBPP system.

[2044] 5.1 Requirement Category (i.e. usability)

[2045] 6. Pre-Conditions

[2046] 6.1 Insert Pre-Condition

[2047] The retailer has to be able to review their invoice prior to executing payment.

[2048] 7. Post-Conditions

[2049] The retailers will have successfully executed their payments to the appropriate suppliers.

[2050] 8. Data Requirements

[2051] The “Execute Payment” screen must enable the retailer to execute payment to a number of manufacturers. They have to be able to retain the manufacturers'banks' detailed information (account number, routing number) to avoid continual reentry of information. They also need to receive a confirmation that the payment was executed, which will enable them to trace the payment with their bank, and the manufacturers' bank.

[2052] Data involved includes all of the retailer's bank information (routing number, account number, invoice number, value date), as well as all of the manufacturers' bank information (routing number, account number, invoice number, value date).

[2053] 9. Interfaces

[2054] The eBPP system will transmit all payment transactions throughout the day to their bank. The files will be formatted into the appropriate AUS BECS/ACH file format standards, and send the file to the bank.

[2055] 1. Context Diagrams

[2056] Context_Invoice and Payment (Electronic payment)

[2057] 2. Use Case Actors

[2058] Retailer

[2059] eBPP system

[2060] 3. Brief Description

[2061] Retailers will access eBPP system to view their invoices online. It is expected that when the retailer views their invoices, they will see all outstanding invoices for all manufacturers. They will have the ability to drill down on specific invoices for more detailed information. The invoice will contain the manufacturers brand, and will contain: date, purchase order number, sales order number, ASN number, invoice number, item, quantity, price, total amount due, payment terms, tax terms.

[2062] 4. Flow of Events

[2063] 4.1 Basic Flow

[2064] The retailer will click onto the “View Invoice” button.

[2065] This will link the retailer into their own secure https page—within the eBPP system domain. eBPP system will ask for their digital certificate information when they link to eBPP system.

[2066] When the “view invoice” screen appears, the retailer will see all of their outstanding invoices listed by manufacturer. This screen will list item, quantity, price, total amount due, and date. For more detailed information on a particular item, such as payment terms, the retailer will be able to click on a particular item to drill down.

[2067] eBPP system has stated that they are able to customize the invoice templates to look exactly like the suppliers' invoices. eBPP system has standard invoice templates available for no additional charge.

[2068] If an invoice is to due that day, the item will be highlighted.

[2069] When the retailer decides to pay the invoice, they will click on an “Execute Payment” button that will take them to the payment initiation screen.

[2070] 4.2 Alternative Flow(s)

[2071] 4.2.1 Example Alterative Flow

[2072] If the retailed would like to dispute an item on their invoice

[2073] 5. Special Requirements

[2074] 5.1 Requirement Category (i.e. usability)

[2075] The retailer will need a button to push “Execute Payment” which will take them to the payment initiation screen.

[2076] 6. Pre-Conditions

[2077] 6.1 Insert Pre-Condition

[2078] An invoice has to have been generated by the Suppliers' ERP system.

[2079] The data file from the Suppliers' ERP systems has to have been received eBPP system.

[2080] 7. Post-Conditions

[2081] 7.1 The retailer will be prepared to execute payment.

[2082] 8. Data Requirements

[2083] The eBPP system invoice presentment must contain: date, purchase order number, sales order number, ASN number, invoice number, item, quantity, price, total amount due, payment terms.

[2084] 9. Interfaces

[2085] The invoice will contain: date, purchase order number, sales order number, ASN number, invoice number, item, quantity, price, total amount due, payment terms. All of this information will be accessed via the initial “view invoice” screen, or the secondary “drill-down” detailed screen.

[2086] Use Case Specification: Receive invoice feed from Suppliers' ERP System to eBPP system

[2087] 1. Context Diagrams

[2088] Context_Invoice and Payment (Electronic payment and cash payment)

[2089] 2. Use Case Actors

[2090] Supplier ERP system

[2091] eBPP system

[2092] 3. Brief Description

[2093] eBPP system needs to receive a feed from the Suppliers' ERP systems that contains all invoice information, both content and layout. The file will contain: date, purchase order number, sales order number, ASN number, invoice number, item, quantity, price, total amount due, payment terms.

[2094] 4. Flow of Events

[2095] 4.1 Basic Flow

[2096] The various Suppliers' ERP systems will generate a file in the eBPP system file format, and send it to the eBPP system system. It is expected that the eBPP system file will be sent real time throughout the day.

[2097] Suppliers will need to send the information in a eBPP system compatible format.

[2098] 4.2 Alternative Flow(s)

[2099] 4.2.1 Example Alternative Flow

[2100] 5. Special Requirements

[2101] 5.1 Requirement Category (i.e. usability)

[2102] 6. Pre-Conditions

[2103] 6.1 Insert Pre-Condition

[2104] Suppliers will need to send the information in a eBPP system compatible format.

[2105] The goods have to be ready for shipment for the invoice to be created.

[2106] 7. Post-Conditions

[2107] 7.1 Receipt of this file will result in an updated eBPP system database, and a formatted invoice that can be reviewed online.

[2108] 8. Data Requirements

[2109] The file must be in the eBPP system predefined file format.

[2110] 9. Interfaces

[2111] The file will contain: date, purchase order number, sales order number, ASN number, invoice number, item, quantity, price, total amount due, payment terms.

[2112] A nightly batch will trigger the file at a set time every night for the Electronic Marketplace Solution file.

[2113] When an invoice is generated for physical good delivery, the print stream will be triggered.

[2114] Use Case Specification: Maintain User Access

[2115] 1. Use Case Diagrams

[2116] Create & Maintain User Profile & Security

[2117] 2. Use Case Actors

[2118] Customer Management

[2119] Platform

[2120] System Admin

[2121] 3. Brief Description

[2122] Develop and maintain user security access and profiles

[2123] 4. Flow of Events

[2124] 4.1 Basic Flow

[2125] 4.1.2 User Profile/Security Entities

[2126] Each user within Electronic Marketplace Solution, will have at least the following profile entities: User, Group, Role, Content, Service, and Application Permissibility

[2127] With's profile model, a user can have one Group, many Roles, many content elements, and so on. Groups and sub-Groups have an inheritance relationship.

[2128] In the RSW, indicated that sub-group functionality is available. Unfortunately, this functionality will not be available until a future release.

[2129] These entities determine, upon user log in to Electronic Marketplace Solution, what functions can be performed and what content is viewed

[2130] 4.1.2 User Profile/Security Maintenance

[2131] As a general rule, the more Groups and Roles that are developed the more maintenance that is required

[2132] An overall Electronic Marketplace Solution System Administrator will have the highest level of system maintenance functionality allowed

[2133] This Electronic Marketplace Solution System Administrator will be the only person who can add new entities or add new users

[2134] To reduce the burden of continual user changes, a company specific Sub-System Administrator can be assigned, if desired.

[2135] This Sub-Administrator can change the associations of any of their company's users to Service and Application Permissibility

[2136] 4.1.3 User Profile/Security Updates

[2137] Each time a change to a profile is requested or required, the System Admin can utilize a user interface to make the changes

[2138] 5. Special Requirements

[2139] 5.1 Release 1

[2140] A digital certificate must be part of the user profile and passed prior to being able to perform payment activities

[2141] Payment is no longer a Release 1 functionality

[2142] The user profile needs to accommodate for the following individuals/roles:

[2143] Convenience Organized: HO Category Manager, HO Finance, HO Purchasing, MSF Account Mgr., MSF Operations Mgr., Store Manager, Store Owner, Site Staff 1, Site Staff 2, IT Support

[2144] Convenience Independent: Store Manager/Owner, Site Staff 1, Site Staff 2, IT Support

[2145] Electronic Marketplace Solution Operations: Security Admin., Catalogue/Profile Maintenance, Finance, IT Support, Help Desk

[2146] Electronic Marketplace Solution Development: Business Development, Content Development

[2147] Electronic Marketplace Solution Misc.: Customer Relations, MIS

[2148] Supplier: Brand Team, Trade Marketing Mgmt. Team, Trade Marketing Reps., IT Team, Finance-Security

[2149] Other: Service Providers, Logistics Providers

[2150] The User needs to understand and agree to be liable for profile and password usage

[2151] The user profile will be based on BAT's current customer hierarchy and fitted to's structure

[2152] The user profile is now based upon Electronic Marketplace Solution's Retailer and Supplier hierarchy fitted to's profile. Because doesn't support user profile hierarchies until future releases, new fields will be added to the user profile to represent the hierarchy.

[2153] 5.2 Release 3

[2154] Sub-Group user profile hierarchy functionality

[2155] 6. Pre-Conditions

[2156] 6.1 The basic profile model has been developed (i.e. all entities have been designed)

[2157] 7. Post-Conditions

[2158] 7.1 User Profile/Security updated and maintained

[2159] 8. Data Requirements

[2160] 9. Interfaces

[2161] Use Case Specification: Create New Profile

[2162] 1. Use Case Diagrams

[2163] Create & Maintain User Profile & Security

[2164] 2. Use Case Actors

[2165] Customer Management

[2166] Platform

[2167] Payment Provider

[2168] System Admin

[2169] Supplier ERP

[2170] User (General)

[2171] 3. Brief Description

[2172] Based upon whether the user is a buyer or a supplier, a user profile is created and all initial data is uploaded

[2173] 4. Flow of Events

[2174] 4.1 Basic Flow—New Buyer/Retailer/Group of Retailers

[2175] A Retailer is identified as a potential Electronic Marketplace Solution customer by Electronic Marketplace Solution CRM or via the Electronic Marketplace Solution Guest Log In procedure

[2176] A Electronic Marketplace Solution Representative contacts the Retailer and begins gathering initial user profile information (i.e. name, address, credit terms, etc.)

[2177] If the Retailer is accepted and agrees to Electronic Marketplace Solution terms and conditions, Electronic Marketplace Solution assigns them a Customer #/User ID/Store ID—Data team will develop hierarchy

[2178] In depth user profile information is gathered and hardware/software installation begins

[2179] The Retailer submits current supplier information (their supplier customer #'s) and that information is validated by the suppliers

[2180] If the information is correct, the Electronic Marketplace Solution-Supplier Customer # translation tables are updated, pricing and catalogue by supplier for Retailer is established, and the user profile is completed

[2181] 4.2 Alternative Flow—New Buyer/Retailer/Group of Retailers

[2182] 4.2.1 Incorrect Supplier Customer ID information submitted

[2183] Electronic Marketplace Solution resolves the issue with the supplier on behalf of the retailer

[2184] Retailer notified of issue and resolution

[2185] 4.2.2 Retailer not accepted as Electronic Marketplace Solution customer

[2186] Retailer is notified of the reasons that they were not accepted as a customer and invited to try again in the future

[2187] 4.3 Basic Flow—New Supplier

[2188] A Supplier is identified as a potential Electronic Marketplace Solution customer

[2189] A Electronic Marketplace Solution Representative contacts the Supplier and begins gathering initial user profile information (i.e. name, address, credit terms, etc.)

[2190] In depth user profile information is gathered and Supplier set up data (catalogue, desired customer criteria, categories; products, etc.) is gathered

[2191] If the Supplier is accepted and agrees to Electronic Marketplace Solution terms and conditions, Electronic Marketplace Solution assigns them a Customer #/User ID

[2192] A conversion team is established to match a supplier's customers to Electronic Marketplace Solution customers

[2193] For the matching customers, a notification is sent to those Retailers and catalogue and pricing is established for those retailers

[2194] For non-matching customers, Electronic Marketplace Solution can offer this information as a value add to the supplier (i.e. open new markets)

[2195] 4.4 Alternative Flow—New Supplier

[2196] 4.4.1 Supplier not accepted as Electronic Marketplace Solution customer

[2197] Supplier is notified of the reasons that they were not accepted as a customer and invited to try again in the future

[2198] 5. Special Requirements

[2199] 9.1 Release 1

[2200] Parent—Child relationship for profiles

[2201] The customer id is a logical join of the store proprietor and the store location

[2202] User profiles for Service Providers and Logistics Providers will follow a similar path but additional data elements may be required

[2203] User profile information will be gathered via paper forms and then entered into the user profile database

[2204] Electronic Marketplace Solution needs to assign a unique customer number for each new retailer. This # will be mapped to the Suppliers' customer id.

[2205] A digital certificate, required for performing payment functions, must be part of the user profile

[2206] Ability to query/data mine entire user profile

[2207] Honor the competitive landscape/information etc. Information sharing will operate similarly to Nielsen. Electronic Marketplace Solution will determine the information sharing parameters

[2208] Retailers have “View” capability prior to being on credit terms with Suppliers

[2209] Potential work around for waiting for supplier credit terms is to place retailers on COD until credit terms have been established/confirmed. This will require supplier buy-in.

[2210] The user profile will be based on BAT's current customer hierarchy and fitted to's structure.

[2211] 9.2 Release 3

[2212] Electronic Marketplace Solution Representatives have a semi-automatic (i.e. on-line form) to gather user profile information which will populate a staging database

[2213] The number of attributes gathered on a Retailer will be limited. Each supplier can specify a limited number (proposed 5) attributes to be gathered.

[2214] 6. Pre-Conditions

[2215] 6.1 Buyer/Supplier is approved by Sales Rep or Guest Log In to be a user

[2216] 7. Post-Conditions

[2217] 7.1 Supplier/Buyer ready for operation

[2218] 7.2 Main catalogue determined, Shopping List populated, Pricing matrix available

[2219] 8. Data Requirements

[2220] Banking/Payment Provider data requirements

[2221] Refer to design specifications

[2222] Proprietor—Debt/Financial Responsibility

[2223] Employees

[2224] Physical Store Location—Store #—Ship to

[2225] Web Page Info

[2226] Supplier Info

[2227] Data Entry

[2228] Customer # is the logical joint of proprietor and store location

[2229] 9. Interfaces

[2230] 9.1 Supplier ERP

[2231] 9.2 Electronic Marketplace Solution CRM

[2232] Use Case Specification: Maintain Current Profile

[2233] 1. Use Case Diagrams

[2234] Create & Maintain User Profile & Security

[2235] 2. Use Case Actors

[2236] Customer Management

[2237] platform

[2238] User (General)

[2239] Supplier ERP

[2240] System Admin

[2241] 3. Brief Description

[2242] The user profile is updated with new information. The user can update some information via an on-line form. The remaining information must be submitted via predefined Electronic Marketplace Solution format (i.e. pricing, catalogue categories, etc.)

[2243] 4. Flow of Events

[2244] 4.1 Basic Flow

[2245] For information that a user can change, the user clicks on My Profile from the Electronic Marketplace Solution default page

[2246] Their profile is displayed with an edit button

[2247] The user can click on edit, update the information, and save

[2248] Typical information could include name, address, telephone #, generic store details, etc.

[2249] For information that a user cannot change (i.e. security access), the user can request changes by sending an email to Electronic Marketplace Solution

[2250] Electronic Marketplace Solution then facilitates the change

[2251] 5. Special Requirements

[2252] 5.1 Release 1

[2253] Access to fields based on user profile

[2254] On-line forms for change requests

[2255] Can customize what fields are editable by User

[2256] Manual work flow to update and change

[2257] 6. Pre-Conditions

[2258] 6.1 User has Electronic Marketplace Solution account and user profile

[2259] 7. Post-Conditions

[2260] 7.1 Profile Updated

[2261] 7.2 Partners notified of change that affects them

[2262] 8. Data Requirements

[2263] 9. Interfaces

[2264] Supplier ERP-Manual data-pull and upload

[2265] Use Case Specification: Activate User Profile & Data

[2266] 1. Use Case Diagrams

[2267] Initiate User Session Package

[2268] 2. Use Case Actors

[2269] Platform

[2270] 3. Brief Description

[2271] Upon successful log in, all pertinent user data is pulled and made “active” for the user session

[2272] 4. Flow of Events

[2273] 4.1 Basic Flow

[2274] User log in accepted

[2275] User information pulled (contact, etc.)

[2276] Pricing data pulled

[2277] Catalogue information/format pulled

[2278] Security active

[2279] Community content pulled

[2280] Promotion data/format pulled

[2281] Payment data pulled

[2282] Order Status data pulled

[2283] Functionality/Access active

[2284] 5. Special Requirements

[2285] 5.1 Release 1

[2286] The user profile will be based on BAT's current customer hierarchy fitted to the user profile structure

[2287] Restricted areas grayed out or not visible

[2288] All relevant data and content pulled upon log in

[2289] 6. Pre-Conditions

[2290] 6.1 User profile has been created

[2291] 6.2 User has successful log in

[2292] 7. Post-Conditions

[2293] 7.1 User specific functionality and data active and populated on UI

[2294] 8. Data Requirements

[2295] User profile

[2296] 9. Interfaces

[2297] Use Case Specification: Log Out-Punch Out

[2298] 1. Use Case Diagrams

[2299] Initiate User Session Package

[2300] 2. Use Case Actors

[2301] User (General)

[2302] POS

[2303] External Sites

[2304] Platform

[2305] 3. Brief Description

[2306] A user either ends a Electronic Marketplace Solution Session, toggles (or punches out) to POS, or punches out to an external site

[2307] 4. Flow of Events

[2308] 4.1 Basic Flow

[2309] In order to completely log out of Electronic Marketplace Solution, user must shut down Electronic Marketplace Solution Internet Session web browser

[2310] 4.2 Alternative Flow(s)

[2311] 4.2.1 Toggle to POS

[2312] Awaiting POS decision

[2313] 4.2.2 Punch Out to External Site

[2314] If a user clicks on another URL, a new window is, open with no interruption to the Electronic Marketplace Solution session

[2315] 5. Special Requirements

[2316] 9.1 Release 1

[2317] Allow session time out. (Time to be determined by Electronic Marketplace Solution Management)

[2318] Currently, if an session times out, all non-confirmed/saved information is lost. A potential work around is to set the session time long enough to avoid this situation

[2319] user session should be maintained during external site punch out

[2320] Punch out functionality (go to another website) while maintaining Electronic Marketplace Solution site security

[2321] When a user clicks on a log out button, another page recommending that users shut down their browser to completely end their session is displayed

[2322] Seamless functionality between POS and Electronic Marketplace Solution—Awaiting POS decision

[2323] 9.2 Release 3

[2324] If a session times out, no information should be lost

[2325] 6. Pre-Conditions

[2326] 6.1 Active Electronic Marketplace Solution Session

[2327] 7. Post-Conditions

[2328] 7.1 User logged out

[2329] 7.2 User viewing external site

[2330] 7.3 Security integrity maintained

[2331] 8. Data Requirements

[2332] 9. Interfaces

[2333] 9.1 External sites

[2334] 9.2 POS

[2335] Use Case Specification: Guest Log In—Registration

[2336] 1. Use Case Diagrams

[2337] Initiate User Session Package

[2338] 2. Use Case Actors

[2339] User (General)

[2340] Platform

[2341] 3. Brief Description

[2342] A new user enters the main Electronic Marketplace Solution Site, can view generic material and register to become a user

[2343] 4. Flow of Events

[2344] 4.1 Basic Flow

[2345] User enters Electronic Marketplace Solution Site

[2346] Selects Log In as Guest

[2347] Views generic material

[2348] User clicks on Register

[2349] User prompted to enter information (i.e. contact info, minimal profile, supplier or buyer, location, name, phone number, etc.)

[2350] 5. Special Requirements

[2351] 5.1 Release 1

[2352] User can view generic information such as marketing material, Electronic Marketplace Solution information, supplier information, brief description of services—Refer to Electronic Marketplace Solution internal marketing to determine actual timing

[2353] On line form to enter registration information

[2354] The guest demo site does not hit the production system

[2355] Key customer qualification fields (i.e. geographical location) will have text disclaimers such as, “Available for Australia/New Zealand Residents Only”

[2356] 5.2 Release 3

[2357] Users can be denied based upon basic requirements such as, location, size, etc.

[2358] 6. Pre-Conditions

[2359] 6.1 Active Internet session

[2360] 7. Post-Conditions

[2361] 7.1 Electronic Marketplace Solution has enough information to contact new potential/interested user

[2362] 7.2 Guest user can view demo site

[2363] 8. Data Requirements

[2364] User Registration information fields

[2365] 9. Interfaces

[2366] 9.1 Marketing server for demo site

[2367] Use Case Specification: Log In—Registered User

[2368] 1. Context Diagrams

[2369] Initiate User Session Package

[2370] 2. Use Case Actors

[2371] User (General)

[2372] Platform

[2373] 3. Brief Description

[2374] A registered user logs into the secure Electronic Marketplace Solution site

[2375] 4. Flow of Events

[2376] 4.1 Basic Flow

[2377] User accesses Electronic Marketplace Solution web site

[2378] User navigates to “registered user log in” portion to access the log in page

[2379] System prompts user to Log In

[2380] User enters ID and Password

[2381] If Log In is correct, user is sent to default page (“My Page”)

[2382] If Log In is incorrect, see alternative flow

[2383] 4.2 Alternative Flow(s)

[2384] 4.2.1 Incorrect User Name/Password

[2385] The system displays message “Incorrect user id/password please try again”

[2386] User re-enters id and password

[2387] If correct, user is sent to default page

[2388] If incorrect, User can try one additional time. If still incorrect, a text box appears instructing the user how to request help and the session expires

[2389] 5. Special Requirements

[2390] 5. 1 Release 1

[2391] Alternative navigation paths based on registered or non-registered user

[2392] Main home page will allow guest users to register and registered users to log in to the secured site

[2393] User id and password format is easily configurable

[2394] Upon final incorrect password entry, a text box appears instructing the user to call the help desk at the following # <<insert #>> to request password assistance

[2395] Internet Explorer 5.0 for pilot—Note—* Establish exact version of pilot for every store and use the same one. Potential enhancements for future.

[2396] More information required on Payment Provider and related log in requirements

[2397] Different layers of security access based upon user profile

[2398] Disallow or recommend not using the save password function

[2399] User must re-enter password for payment functionality or user needs to be verified by some digital certification. Do not want to have system remember user name and password. There is a concern about the security of the fund transfer functionality

[2400] Various help desk screens—this is bigger than just log in

[2401] 5.2 Release 3

[2402] Upon final incorrect password entry, user can navigate to a password help screen and request assistance via an online form

[2403] User can bookmark secure portion of Electronic Marketplace Solution to avoid main homepage

[2404] Seamless log in function between POS and Electronic Marketplace Solution—Awaiting POS decision

[2405] 6. Pre-Conditions

[2406] 6.1 User has started Internet session

[2407] 6.2 User has registered with Electronic Marketplace Solution

[2408] 6.3 User profile has been established

[2409] 6.4 Help desk or help tips have been established and are accessible

[2410] 6.5 Security has been activated

[2411] 7. Post-Conditions

[2412] 7.1 User sent to default page (“My Page”)

[2413] User accesses customized specific operational page for them. This is based on the user profile. Current events, news, and content. This is the page from which the user accesses the menu.

[2414] 7.2 User Profile is “activated”. User specific data and access is pulled

[2415] Specific pricing data

[2416] Specific Store/Co and My List data

[2417] Security profile

[2418] Access/functionality

[2419] Targeted Content

[2420] 8. Data Requirements

[2421] Password

[2422] User ID

[2423] User Profile information (content, advertising, functionality, access, etc.)

[2424] Security Access information

[2425] 9. Interfaces

[2426] Payment provider

[2427] It should be noted that the computer network as referenced in this specification should be taken to include all forms of connected or communicating computers or terminals having at least two terminals connected or communicating as hereinbefore described. That is, the term computer network should be taken to include any type of terminal as hereinbefore defined, computer, computerised device, peripheral computer equipment, computerised accessory, mobile or cellular phone, digital electronic device or other similar type of computerised electronic device or part thereof which is rendered such that it is capable of communicating with at least one of any of the aforementioned entities. Said communication of information or data can occur over any data communications network, computer network, wireless network, internetwork, intranetwork, local area network (LAN), wide area network (WAN), the Internet and developments thereof, transient or temporary network, combinations of the above or any other type of network providing for computerised, electronic or digital devices.

[2428] Furthermore, references to the terms connecting, communicating, transmitting, requesting, receiving, exchanging and the like, and permutations thereof, as applied to the term computer network and/or components thereof should be taken to pertain to the transfer of information or data. Such transfers of information or data can be facilitated for by any form of entity/entities for facilitating such, including, but not limited to, metallic wires or cables, semi-conducting wires or cables, optical fibres and optical devices, wireless means, electromagnetic waves and the like and modulations thereof, acoustic waves and the like and modulations thereof; control of electric and/or magnetic fields, and/or the transportation of all forms of memory devices.

[2429] Thus, there has been provided in accordance with the present invention, a new type of Internet based business to business portal which satisfies the advantages set forth above.

[2430] The invention may also be said broadly to consist in the parts, elements and features referred to or indicated in the specification of the application, individually or collectively, in any or all combinations of two or more of said parts, elements or features, and where specific integers are mentioned herein which have known equivalents in the art to which the invention relates, such known equivalents are deemed to be incorporated herein as if individually set forth.

[2431] Although the preferred embodiment has been described in detail, it should be understood that various changes, substitutions, and alterations can be made herein by one of ordinary skill in the art without departing from the scope of the present invention as hereinbefore described and as hereinafter claimed. 

1. An integrated system for providing an electronic marketplace solution, the integrated system including: means for Point of Sale (POS) scanning of goods and associated data capture by a Convenience Retailer; means for determining a replenishment order for goods, based on sales by the Convenience Retailer, preordained Convenience Retailer criteria, or the Convenience Retailer manually selecting goods; means for the electronic transfer of the replenishment order to a Supplier via a Supplier ordering system; and means for providing a payment processing module which links the Supplier ordering system and a payment gateway which is able to communicate with the Convenience Retailer's commercial banking system.
 2. The system as claimed in claim 1, wherein electronic processing of returned goods is integrated into an order tracking procedure.
 3. The system as claimed in either claim 1 or claim 2, wherein the Supplier is a FMCG Manufacturer or a Wholesaler.
 4. The system as claimed in any one of the claims 1 to 3, wherein the system includes a centrally managed database which is linked with the Supplier ordering system.
 5. The system as claimed in any one of the claims 1 to 3, wherein POS/BOS data is managed within a centrally managed database.
 6. The system as claimed in any one of the claims 1 to 5, wherein goods are scanned on receipt by the Convenience Retailer and/or on sale to a consumer.
 7. The system as claimed in any one of the claims 1 to 6, wherein the associated data is used to deliver market information to the Convenience Retailer, the Supplier, a Manufacturer, a Wholesaler or a Logistics Provider.
 8. The system as claimed in claim 7, wherein the system provides network-based access to the market information via a business-to-business web portal.
 9. The system as claimed in any one of the claims 1 to 8, wherein part of the system is in a private network and access to the part of the system requires user authentication.
 10. The system as claimed in any one of the claims 1 to 9, wherein the system includes means for Available To Promise (ATP) checking from the Supplier's inventory database.
 11. The system as claimed in any one of the claims 1 to 10, wherein the system includes means for providing electronic confirmation of replenishment order acceptance from the Supplier to the Convenience Retailer.
 12. The system as claimed in any one of the claims 1 to 11, wherein the system includes means for electronic tracking of replenishment orders until delivery of the goods to the Convenience Retailer.
 13. The system as claimed in any one of the claims 1 to 12, wherein all electronic transfers and ordering occur via the Internet.
 14. An integrated system for providing an electronic marketplace solution, the system including: means for Point of Sale (POS) scanning of goods and associated data capture by a Convenience Retailer; means for a Convenience Retailer to search and browse a multiple Supplier goods and pricing catalogue for determining a replenishment order for goods; means to provide the Convenience Retailer with online replenishment order placement to a Supplier; means for the tracking and management of goods; means for providing electronic bill presentation and payment; and, means to generate customised reports for the Convenience Retailer or the Supplier.
 15. The system as claimed in claim 14, wherein the system includes means to facilitate Supplier access to marketplace based promotions.
 16. The system as claimed in claim 14, wherein the system includes a telecommunications infrastructure providing: a secure private network; a secure connection via the Internet; and Internet connectivity.
 17. The system as claimed in any one of the claims 14 to 16, wherein the system includes inventory management and business reporting tools for the Convenience Retailer.
 18. The system as claimed in any one of the claims 14 to 17, wherein the system is integrated with at least one Supplier enterprise resource planning (ERP) system to provide: Available To Promise (ATP) checking from the Supplier's inventory database; credit and payment status checking from the Supplier's financial database; electronic transfer of orders to the Supplier's order capture system; and Supplier confirmation of order acceptance and fulfilment.
 19. The system as claimed in any one of the claims 14 to 18, wherein the system communicates with commercial banking systems to provide the electronic payment.
 20. The system as claimed in any one of the claims 14 to 19, wherein the system includes business and technology integration with convenience industry Service Providers to promote and supply related goods or services.
 21. A method of providing an electronic marketplace solution, the method including the steps of: a Convenience Retailer performing Point of Sale (POS) scanning of goods and associated data capture; determining a replenishment order for goods, based on sales by the Convenience Retailer, preordained Convenience Retailer criteria, or the Convenience Retailer manually selecting goods; electronically transferring the replenishment order to a Supplier via a Supplier ordering system; an automated request being transmitted, by a Convenience Retailer terminal or the Supplier ordering system, to a Logistics Provider to effect delivery of the goods; the Logistics Provider arranging delivery of the goods to the Convenience Retailer; and, performing payment processing which links the Supplier ordering system and a payment gateway which is able to communicate with the Convenience Retailer's commercial banking system.
 22. The method as claimed in claim 21, wherein the Convenience Retailer terminal can be used to access a database providing the delivery status of the goods.
 23. The method as claimed in claim 21, wherein goods are scanned by the Convenience Retailer, the Supplier and the Logistics Provider, thereby providing marketplace information able to be accessed in a database.
 24. The method as claimed in claim 23, wherein goods are scanned by a scanner connected to the Convenience Retailer terminal when received by the Convenience Retailer, thereby updating relevant records in the database.
 25. The method as claimed in claim 21, wherein relevant records include: inventory information; sales figures; time of sale; place of sale; or identifying information about the consumer.
 26. The method as claimed in any one of claims 21 to 25, wherein information pertaining to consumer purchases gathered by the Convenience Retailer is visible to the Supplier; a Wholesaler; the Logistics Provider; and/or a Service Provider.
 27. The method as claimed in any one of claims 21 to 26, wherein automated ordering of goods occurs when database records indicate that the Convenience Retailer's stock of goods is at a predetermined level.
 28. The method as claimed in any one of claims 21 to 27, wherein the Supplier, a FMCG Manufacturer, a Wholesaler, a Logistics Provider, and/or a Service Provider, individually or cooperatively collate orders for goods from the Convenience Retailer.
 29. The method as claimed in any one of claims 21 to 28, wherein data or information pertaining to past sales transactions in the convenience marketplace are available, via a computer network, to authorised users or participants from an information source.
 30. A network based business to business Internet portal, the Internet portal providing access to an electronic marketplace solution, the Internet portal providing: a facility to submit a replenishment order to a Supplier via a Supplier ordering system, the replenishment order based on sales of goods by the Convenience Retailer, preordained Convenience Retailer criteria, or the Convenience Retailer manually selecting goods; a facility for the Supplier to confirm the availability of goods; a facility to provide goods delivery status information; and, a payment processing system which links the Supplier ordering system and a payment gateway which is able to communicate with the Convenience Retailer's commercial banking system allowing the Convenience Retailer to pay for goods.
 31. A set of computer readable medium of instructions for use in providing an electronic marketplace solution, the set of instructions enabling web-based order processing and including procedures for: Point of Sale (POS) scanning of goods and associated data capture; determining a replenishment order for goods, based on sales by a Convenience Retailer, preordained Convenience Retailer criteria, or the Convenience Retailer manually selecting goods; electronically transferring the replenishment order to a Supplier via a Supplier ordering system; and, web-based browse and buy functionality providing payment processing which links the Supplier ordering system and a payment gateway which is able to communicate with the Convenience Retailer's commercial banking system.
 32. The set of instructions as claimed in claim 31, wherein the procedures also include available To Promise (ATP) checking from the Supplier's inventory database, and Supplier confirmation of the replenishment order acceptance. 